Your website speed optimization service manager

Web performance from the client point of view is measured as the page load time. This is the lapsed time between the moment a user requests a new page and the moment the page is fully rendered by the browser. Fast web pages render progressively. That is, they display their content incrementally, as it is loaded by the browser. A web page that renders progressively gives the user visual feedback that the page is loading, and gives the user the information they requested as soon as it is available. Google® and Yahoo® both suggest best practices to make web pages render progressively, such as putting style sheets in the document head. There are several additional best practices that you can apply to optimize progressive rendering for most pages.

First, a fast page should render the content that is visible to the user first, and render the off-screen content (that is, the content outside of the current scroll region) later. Second, a fast page might also load and render the lightweight resources such as text before loading and rendering heavyweight resources like images and video.

Viralify’s website optimization service uses a combination of web security and page speed best practices to speed up page load times.

Website optimization is a continuous process. While you will start seeing results in a week’s time, it’s important that you stick to the maintenance routine to see consistent results.Thee act of regularly checking your website for issues and mistakes and keeping it updated and relevant should be done on a consistent basis in order to keep your website healthy, encourage continued traffic growth, and strengthen your SEO and Google rankings.

Because Google wants fast websites! What Google wants is what your website’s users want (Why Performance Matters by Jeremy Wagner at Google). It is an optimal User Experience for your site’s real users. Simply stated, the user’s perception of speed is the by-far-and-away most important performance characteristic. This is, of course, why Google is so adamant about optimizing above-the-fold content and why Google so highly favors websites that have implemented Progressive Rendering to the fullest extent possible. What Google cares about most are what your site’s users care about most:

• The speed with which your above-the-fold content begins to render.
• The time it takes for above-the-fold content to be visually complete and interactive.
• The average time at which visible parts of your page are displayed relative to the average time at which visible parts of your competitor’s page are displayed.

Some combination of the following will be needed. We will let you know exactly in the email you will receive after ordering:

Administrator-level WordPress login credentials (username and password).
If applicable: Domain registrar login credentials (login URL, username and password).
If applicable: Hosting account login credentials (username and password).
If applicable and if you have cPanel: cPanel login credentials (username and password).
If applicable and if you have cPanel with WHM: WHM login credentials (login URL, username and password).
If applicable: (S)FTP login credentials (host, username, password and port).
If applicable: CloudFlare (or Sucuri, etc) login credentials (username and password).
If applicable: Secondary CDN (e.g. MaxCDN) login credentials (username and password).

Note: All credentials you provide to us are deleted from our server upon project completion. Once your project is completed, you are also encouraged to change any passwords you have provided to us.

Yes and no. First, we clone your site and insert it into a testing environment, thereby enabling us to do A/B testing with no potential for disruption to your live website. 95%+ of the of the project is actually done in this testing environment. However, once we feel we have everything dialed-in, we do have to implement the changes on your live website, which constitutes ~5% of the project.

Yes. Making a backup prior to making any changes to your website, or having changes made, is very highly recommend and basic best practices

We do, but such projects are automatically ineligible for refund/our guarantee even if we were, through no fault of our own, unable to actually implement your site’s new performance architecture.

Project sites hosted on restrictive hosting platforms (i.e. hosts like WP Engine, FlyWheel, Kinsta etc. that disallow caching plugins, for example) are ineligible for refund/our guarantee primarily because they limit our ability to fully optimize your website or do so in a way that is fine-tuned for your particular website’s needs.

Ads/3rd party resources (things used by your site but not actually served from your server) cannot, themselves, be made faster, no, since we cannot access the server from which they are being served.

But! — making your website and everything actually served from your server as fast as it can possibly be will make ads/3rd party resources begin and therefore end their loading sooner, which gives your site a net performance gain.

We notify you when the project is complete and provide you with a summary of what was done; and, we explain any special instructions that you need to know moving forward.

The reporting includes all this; plus, detailed before and after metrics for every single resource or asset that makes your site what it is, before and after video, various charts and graphs detailing the improvements made, project notations, recommendations and the like. In short, every possible thing you could want or need to know about how our work has affected your site.