Site speed is already included in the results since it potentially affects the user experience metrics (page views per visits, bounce rate, time on site). Therefore, 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 latter two might affect pageviews per visits, so they are tested, but they are not measured as a goal as their impact is unclear.
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.
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.
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.