Include site speed when calculating performance compared to old site
I love the increase in revenue that Ezoic has given me, but the site has slowed down considerably, which is impacting traffic (people giving up while they wait for the page to load) and therefore revenue. I'm also worried that the slowdown will eventually be reflected in my site's rankings which will further impact revenue.
It would be great if the site speed was included as part of the Performance metric so it could become something that the Ezoic platform could optimise for (e.g. fewer ads = less javascript = faster performance = potentially more revenue).
-
Anonymous commented
Pathetic speed load speed. 4.1 secs really and 95% bounce rate ? And i see no chances of improving. Abandoning this tool. As pushup is far better i guess atleast we have control.
-
Site speed is already included since it potentially affects the user experience metrics (page views per visits, bounce rate, time on site). Therefor, if the site speed is poor, those metrics will suffer.
Ezoic as a platform measures the desired end results, not the means. For example, we measure page views per visit, not "how many links are above the fold" or "how many menu items are there". The later two might affect pageviews per visits, so they are tested, but they are not measured as a goal as their impact is unclear.
However, specifically addressing site speed:
1. Make sure you are on your main domain. Often the domain listed in the search engines is www.domainname.com and publishers themselves go to the site without the www. - because no one visits the site without the www, there isn't much caching going on.
2. For a similar reason, make sure you are going to pages that are used frequently by your users. If you're just randomly clicking around you may be viewing pages that no one goes to and aren't cached.
3. If you're using a measurement tool, they often measure the time until all elements on the page have completely loaded. The Ezoic platform intentionally lazy-loads unnecessary resources. For example, if there is a Facebook like button at the bottom of the page, we will delay the loading of that item until later. This makes the total time for the page to load longer, but improves usability since the content that the user first sees loads first / faster.
In case you're not aware, Ezoic does the following:
1. Serves all your static content (images, css, etc) from a wold-wide cdn.
2. Uses latency-based routing to route each user to one of four world-wide data centers that is the fastest for them.
3. Combined external resources into single requests. For example, if you have 8 javascript files on your page that requires 8 round-trips from the browser. Ezoic combines those into a single file (and a single requst).
4. Ezoic compresses external resources (like css files) to decrease their file size.
5. Ezoic partners with Cloudflare, which is the largest CDN and security company in the world. You can enable them in the App section. They do a lot of the stuff I just describes above and more.
-
Chocobo commented
Same here...my pageload times have increased considerably, and that is worrisome to me.
-
Tony Lawrence commented
I agree speed is bad. I hoped this was because of testing, but if this is how it is going to be, I might have to abandon this - not something I want to do :(