Site Speed Bot Website Speed Test

critical
We didn't detect a CDN or Content Delivery Network (we may be wrong though)
A CDN is a network of servers located around the world that serve up part of your website and files which both takes the load off your primary web server and speeds up your site globally. A CDN is a key component of a fast loading website. Here we probe for the presence of a CDN or Content Delivery Network - because of the complexities of how a CDN works this test may not be 100% accurate so doublecheck the result! Popular CDNs are: Cloudflare MaxCDN KeyCDN Note that this test is often inaccurate so manually check this result. There's thousands of different CDN services so near impossible to keep up to date with them all.
Uh oh, your HTML time was over 1 second, this is definitely a problem.
Your HTML needs to download before your site will render so the faster this happens the faster the actual AND perceived load time will be for your visitor. We measure this because poor quality or overloaded hosts will cause the HTML download time to be slow. If you're using Wordpress then you pretty much MUST use a caching plugin to get reasonable time on this metric and overall good load time for your site. WP Rocket is an excellent option here and if you're DIY-ing or less technical will usually be the best caching plugin to use. We often find that when people DIY their own speed optimization they blindly follow recommendations from online tools (many of these out of date) and end up generating huge HTML files that take a long time to download. The smaller your HTML file the faster it is to download. **NOTE this problem can also be a symptom of slow DNS hosting and/or high TTFB (high TTFB can be because of slow DNS hosting too!) This article details how to improve your time to first byte and server response times.
You have at least one file that is generating a 404 error. A single 404 error can easily add 1-5 seconds of load time to a page and often more. 404 errors can also substantially impact SEO and Google rankings.
We detected a file that's 404-ing which means the server can't find it. In some instances especially where you have a custom 404 page that's going to add big delays into the page load and it's going to take much longer to load. Speed isn't the only reason to get this resolved. You should fix broken internal links to help Google to crawl and index your site. Any broken external links should be fixed as well. Scroll down below and review the waterfall to determine what files are 404ing out and fix them. The 404ing file(s) will have a red dot next to it in the waterfall view.

high
No Next-Gen image file formats detected. (**this can be wrong if you don't have many images)
We didn't detect any Next-Gen image file formats which means your page size is probably bigger than it needs to be. You're probably familiar with JPG and PNG images but most people don't realize there are newer, more optimized formats such as .webp Often .webp files will be 50%+ smaller than the equivalent JPG or PNG. Unfortunately not all browsers and devices support Next-Gen image formats so this needs to be done via plugin or a CDN (content delivery network) Shortpixel provide a tool to test how compress-able your images are. This blog post explains how to inject webp images in Wordpress using their plugin. **NOTE that if your page has very few images or only a couple of images above the fold this test may not detect Nextgen image support accurately. This video explains how you can manually check for Nextgen Image File Formats:
Uh oh! Your TTFB (time to first byte) is really high. It's over 500ms (half a second) which is a problem.
We expect to see TTFB to sit between 0.1-0.2 seconds (100-200ms) in the country where you're hosted and 0.2-0.5 (200-500ms) internationally. Step 1, run this test one or two more times to make sure it's not a oneoff problem. If the TTFB is still high then there's likely a technical issue with the site. Click here to learn more about how to reduce your TTFB *** Using better quality hosting and using a caching plugin are two simple ways to reduce your TTFB Hosts that are known to be FAST and will have a low TTFB are Siteground - one of the fastest Cpanel web hosting companies Cloudways - dirt cheap, dedicated server power without the complexity Rocket.net - high quality, high speed hosting with Cloudflare Enterprise Edge Caching built in WordPress Caching Plugin If you're using Wordpress the WP Rocket caching plugin is the way to go if you're a DIYer looking to increase your speed. It's a paid plugin but dirt cheap in comparison to the benefit it provides. Alternatively, if you want the fastest caching plugin FlyingPress is the way to go. It's more advanced that WPRocket with some additional features to boost speed and pass Google Core Web Vitals.

warning
Hmm your page seems to be less than 100kb. Either it's REALLY tiny or something went wrong. You probably want to double-check this test.

informational
Great, no admin_ajax.php requests detected
Requests made via the admin-ajax.php library are usually quite CPU intensive and slow so we ideally want to avoid them where possible.
Great! Your server supports the HTTP2 protocol, nothing to do here.
We didn't detect any HTTP/2 "pushed" files, if you're optimizing to the absolute limit it might be worth looking at this.
HTTP/2 Push is a feature of the HTTP/2 protocol. With HTTP/2 Push in place, files and resources required to render the webpage are automatically sent to the visitor before they even request them. This optimization is a key component of getting that instant, snappy load feeling for people visiting your website. Your web server needs to support HTTP2 in order for this feature to be available. If you're using Wordpress there are several plugins that will add this functionality to your site. ***NOTE that if you're using Cloudflare HTTP2 push may not be possible. Custom code can be added to your site to configure Cloudflare with HTTP2 push BUT on many hosts this can cause problems and intermittent "500 Internal Server Error" messages in 1 out of 10 or 20 page loads

good
Your Load Time (aka Onload time or document complete) is less than 3 seconds which is ideally where we want it to be!
Your Load Time (aka Onload time or document complete) is less than 3 seconds which is ideally where we want it to be!
Hmm, you've got less than 30 files loading on this page which means you're either a speed NINJA (awesome!) or something went wrong.
If you don't think you're really a speed ninja run this test again just in case.
This page will take less than 5 seconds to download on a 25mb/second connection which would be considered a relatively fast broadband internet connection speed.
Your hosting provider is not on our slow hosts list.
With this test we probe your hosting provider to see if it's on our slow hosts list. Note that this test is not always accurate as there are thousands of providers across the web. Hosts that are well known across the web to be slow and unreliable include: Bluehost Godaddy Hostgator Site5 1and1 Any host that is part of EIG - Endurance (see EIG Hosts Crazydomains Netregistry Melbourne IT Network Solutions Three fast web hosting companies to consider that have a focus on speed and performance and do have http2 protocol support are: Cloudways - lightning fast, managed, dedicated servers Siteground - a fast general purpose web hosting provider Kinsta - a high speed managed WordPress host If you're looking for country specific recommendations, here's some additional information: The Fastest WordPress hosting Worldwide - a more detailed list of who we recommend, why we recommend them and who they're best suited to The Best WordPress hosting in Australia - a common mistake Australian businesses make is hosting overseas instead of a local provider which means your site is automatically 1-2 seconds slower. The Best & Fastest WordPress hosting in the UK - the UK and Europe are unique in that they often serve a broader geographic area than just a single country. Again a common mistake UK businesses make is hosting in the US which again makes the site much slower.
Your Core Web Vitals First Contentful Paint (FCP) time is under 1.8 seconds which is great!. This means in the real world your site appears quickly to your visitors and they will perceive your site to be fast.
The FCP time is the start of your site render, it's when the user sees something happening. FCP time encompasses a number of elements and there are many ways to improve this metric including reducing DNS lookup time, reducing TTFB, minimizing or eliminating render blocking CSS and Javascript as well as reducing the weight or filesize of elements “above the fold” on a page by doing things like using Lazy Loading and Nextgen Image Optimization. In most cases your FCP time should be lower than the Fully Loaded Time, if it's not usually the culprit is excessive amounts of javascript causing high CPU usage. This article goes into detail on how to reduce your First Contentful Paint or FCP Timing
Your Core Web Vitals average LCP is under 2.5 seconds, which is considered fast, nice work!. Users will feel like the site loads lightning fast!
Your LCP is under 2.5 seconds, which is considered fast, nice work!.
LCP or Largest Contentful Paint, is a core web vitals metric that represents the time needed for the biggest part of the webpage (an image, video, etc.) to appear in the visitor’s browser. It’s one of the most important factors when it comes to your site’s speed because it’s when the visitor perceives the page as loaded. To make Google happy, your largest contentful paint timing should sit under 2.5 seconds, so the largest content on the page should be visible and ready for interaction in no longer than 2.5 seconds. To pass Google’s Core Web Vitals Test for LCP timing, 75%+ of your visitors should get an LCP time of under 2.5 seconds. This article provides a detailed guide on reducing and improving your Largest Contentful Paint timing.
Your Fully Loaded Time is between 1.5-2 seconds
Ideally we want our speed timings looking something like this: -TTFB 0.1-0.2 seconds (this is where is should be in the country where the site is hosted, 0.2-0.5 internationally) -FCP at or under 1 second -LCP under 4 seconds but ideally as close to the LCP as possible, generally within 1 second of the LCP is fast -load time 1.5-2.5 -fully loaded time can vary a lot depending on the third party code being used. Generally we'd expect to see it 1-2 second higher than the load time but this largely depends on the type of site, eg with a Woocommerce site this could easily be 3-5 seconds higher depending on the marketing code in use Usually a higher fully loaded time is due to third party files loading - like analytics tools, marketing code and so forth. It's worth reviewing the waterfall view below and the breakdown of file types beneath that to see if there's an obvious areas for improvement. When you look at the waterfall view, the longer or fatter the line the slower that file is loading. You ideally want to eliminate or fix any files that are taking excessively long to load. It's worth running the test a few times to get an average and also running from multiple locations. Occasionally a location will run fast or slow or the route may be congested so the test result may not be 100% accurate. Don't take this recommendation on face value, you really REALLY need to investigate and review the waterfall breakdown further below to understand how the site speed is really doing.

This SERP analysis feature will give you basic recommendations around SEO on some fundamental SEO fields, the title tag of your page, your meta description and your open graph image.

These SEO fields determine how the website appears *most* of the time (sometimes Google will change it) in the search results. The title tag also tells Google what the page is about so can heavily influence what keywords or search terms your page ranks for and how high.

The meta description doesn't influence rankings directly BUT does tell searchers on Google what your page is about and when well written, will determine what percentage of people who see your page in the search results will click through to your website. This percentage or metric is known as Click Through Rate (CTR).

We added this basic analysis field as many people using our speed test tool are ultimately chasing better search engine rankings and more website visitors. We see again and again these SEO fields being used poorly or not at all which is frustrating to see as simply having these fields populated (even without optimizing or fine tuning them) can make a big difference to your Google Rankings and SEO traffic.

Open Graph Preview Section

Below you'll see a preview of the Open Graph Image and Tags if you have them setup on the site. OG tags are what is displayed when this page is shared on social networks and chat tools. A custom open graph image on each page, particularly your homepage, can dramatically improve CTR (click through rate). If nothing shows below you either don''t have these tags or our tool couldn't properly detect them.

We recommend BannerBear for generating high quality, high CTR Open Graph images on autopilot! - click here to visit Banner Bear

high
Uh oh, it looks like you have a blank or empty meta description field, that's definitely bad for SEO and should be fixed.
In this test we're probing for the existence of a meta description. If you're getting an error here we couldn't detect a meta description on this page. Double check this result by doing this search with the web page URL/address in Google: site:yourdomain.com/page This will usually show you how the page is normally appearing in Google Search. If you don't have meta description set typically Google will use the first paragraph on the page.

other
Uh oh, it looks like you have a blank or empty title tag field, that's definitely bad for SEO and should be fixed.

Summary
Page Size: 36.2 KB
Here we measure the total size of your page (excluding lazy loaded files) and smaller is better here. Generally a fast loading page will sit somewhere between 0.5mb-2mb in size. Google's guideline for page sizes is under 1.6mb. In the real world typically we see any page over 3mb will almost certainly fail to pass Google's Core Web Vitals test. How To Reduce Page Size aka "Avoid Enormous Network Payloads" in Google Lighthouse or Pagespeed Insights Two simple ways to reduce the file size are to compress images, ideally with Nextgen image compression (we do probe for this, click the Nextgen image section for details on how to do this) and also use Lazy Loading to defer the load of images, Youtube embeds and videos and iFrames. With lazy loading in place, images and files that sit outside the viewable area or "above the fold" are not loaded until the visitor scrolls down to that section of the page. This helps make the initial load of the page much lighter and faster. Troubleshooting Excessively Large Page Sizes Excessively large pages would be 5mb, 10mb or larger. Here you really need to first identify the root cause. Scroll down to the bottom of the report and it'll give you a breakdown of file sizes by type - it's an easy way to identify whether large images are your problem or something else. The most common causes of problems here are excessively large images, for example images that are say 5000x3000 pixel resolution where the section they sit in on your site is 500x300 pixels, too many embeds on a page like several Youtube embeds or very heavy video backgrounds. Best Image Compression and Optimization Plugins for Wordpress The two image optimization plugins we typically recommend for WordPress are EWWW Optimizer and Shortpixel. We prefer EWWW Optimizer as it's more fully features and on some hosts can use server resources to compress images faster. Best Lazy Load plugin for Wordpress If you're using WordPress, two easy ways to implement lazy loading for images, videos and Youtube embeds and iFrames are using either WP Rocket or PerfMatters. We use both WPRocket and PerfMatters but prefer PerfMatters. for lazy loading as it's more Core Web Vitals friendly as it allows us to exclude the first X number of images on the page from lazy loading as we want to avoid lazy loading images (we usually set to 4 or 6 images) above the fold. We strongly recommend excluding your logo image from lazy loading as that will help improve your FCP timing too. Read more about PerfMatters lazy loading features here. For additional information on fixing this error and reducing page sizes see this blog post titled How To Fix The ‘Avoid Enormous Network Payload’ Warning In Google Pagespeed Insights
Fully Loaded Time: 1.704s
Here we're measuring the total load time of your site using the Fully Loaded Time metric. Fully loaded time is the point where the "Onload" event fires AND there's been no network activity for 2 seconds. This timing is a good general measure of overall speed BUT note that other timings such as FCP (first contentful paint, aka the start of the site render) are also important as these relate to the user's perception of load speed. In a perfect world we want the site loading in under 1 second. On good quality hosting on a well optimized site, with a content delivery network (CDN) we'd expect to see load times site between 600-800ms in the country the site is hosted in. Internationally this number would be 0.5-1 second higher. If you're looking for a FAST web host, check out these guys: Siteground - one of the fastest Cpanel web hosting companies Cloudways - dirt cheap, dedicated server power without the complexity WPX Hosting - high quality, high speed managed Wordpress hosting at a great price Almost all types of sites will benefit from caching. Caching prebuilds each page so when a visitor arrives that the site all the code execution, database lookups and other work are already done and the HTML file is ready to go. If you're using WordPress, WP Rocket is an excellent DIY caching plugin and worth a look.
FCP Timing (Render Start): 0.0s
First contentful paint or FCP is an important metric as it's the start of the site render and is when the user sees something happening. FCP time encompasses a number of elements and there are many ways to improve this metric including reducing DNS lookup time, reducing TTFB, minimizing or eliminating render blocking CSS and Javascript as well as reducing the weight or filesize of elements “above the fold” on a page by doing things like using Lazy Loading and Nextgen Image Optimization. In most cases your FCP time should be lower than the Fully Loaded Time, if it's not usually the culprit is excessive amounts of javascript causing high CPU usage. This article goes into detail on how to reduce your First Contentful Paint or FCP Timing
Last Hero Painted (Broadly - Render Above The Fold Completed): 0.0s
Last Hero Painted is a render timing metric. Render metrics are important because they relate to how your visitors perceive load time and their overall user experience. This is a synthetic metric in that it’s a close approximation of when the user will experience the render above the fold (the viewable area of the site) complete. It goes hand in hand with the first contentful paint metric (the start of the render) and its essentially the end of the render as the user perceives it. It’s important to note that this metric can be inaccurate if you have popups, slide-ins and other animated or moving elements that impact the render of the site or the feeling of “load complete-ness”. This metric may also report zero if the tool had difficult rendering the site due to javascript errors or other errors that interfere with the render for example 404 errors. You can learn more about this metric at this blog post
Number of Requests: 2
Here we're counting the total number of files aka requests your web page is making. Less is better with this metric. A fast loading page will typically have 50-100 files that load. The more simple the page the less files that should load. A simple way to reduce this count is to use Lazy Loading to defer things like image loading and video loading.
TTFB (time to first byte): 1.312s
Here we're probing TTFB or Time To First Byte. This is a measurement of how quickly or how soon your web server starts sending data. Faster is better. Generally speaking your TTFB should be under 250ms in the country you're hosted and will typically sit between 250-500ms internationally. Slow DNS hosting and HTTP2 support have a direct impact on TTFB time so if your DNS hosting speed was poor and your host doesn't support HTTP/2 then this number will be higher than it really should be. Using better quality hosting and using a caching plugin are two simple ways to reduce your TTFB Hosts that are known to be FAST and will have a low TTFB are Siteground - one of the fastest Cpanel web hosting companies Cloudways - dirt cheap, dedicated server power without the complexity Rocket.net - high quality, high speed hosting with Cloudflare Enterprise Edge Caching built in WordPress Caching Plugin If you're using Wordpress the WP Rocket caching plugin is the way to go if you're a DIYer looking to increase your speed. It's a paid plugin but dirt cheap in comparison to the benefit it provides. Alternatively, if you want the fastest caching plugin FlyingPress is the way to go. It's more advanced that WPRocket with some additional features to boost speed and pass Google Core Web Vitals.
DNS Resolution Time (aka DNS speed): 0.0s
Here we probe the speed of your DNS resolution. Nearly everything on the Internet starts with a DNS request. DNS is the Internet’s directory and if your DNS hosting is slow, your website will be slower to load. Cloudflare.com is generally the fastest DNS host in the world. You can see the top hosts compared and continually tested at "https://dnsperf.com">DNSPerf.com
SSL negotiation time: 0.0s
Connection Time: 0.0s
Here we're measuring how long it takes to connect to your server. Lower is better here. Usually when this metric is high there's a network error, your hosting is broken or you're on bad hosting. If the connection time was high (bad), run this test again to make sure it wasn't just a one off.
Wait time: 1.312s
Receive time: 0.004s

Other metrics
OnLoad Time: 1.704s
HTTP2 protocol supported by the server?: yes
In this test we probe your web host for HTTP2 protocol support. HTTP 2 is a newer version of the HTTP server protocol and dramatically speeds up how quickly files are downloaded by your website visitors. This protocol has been available since mid 2015 and by now your host should have upgraded your server to support it. The HTTP/2 protocol and support for it supercedes older speed recommendations you'll fine around the web such as domain sharding and parallelizing downloads across hostnames. This video highlights the difference in speed between HTTP 1.1 and HTTP2: The video is a demo from the Imagekit website, you can see the demo in person here: https://imagekit.io/demo/http2-vs-http1 If you don't pass the HTTP2 protocol support test you should log a support ticket with your host and ask them about it. If you get no success there then you should look elsewhere as hosting speed is likely not a priority for them. Three lightning fast hosts to consider are: Cloudways - lightning fast, managed, dedicated servers Siteground - the fastest Cpanel host in the world Kinsta - a high speed managed WordPress host If you're looking for country specific recommendations, here's some additional information: The Fastest WordPress hosting Worldwide - a more detailed list of who we recommend, why we recommend them and who they're best suited to The Best WordPress hosting in Australia - a common mistake Australian businesses make is hosting overseas instead of a local provider which means your site is automatically 1-2 seconds slower. The Best & Fastest WordPress hosting in the UK - the UK and Europe are unique in that they often serve a broader geographic area than just a single country. Again a common mistake UK businesses make is hosting in the US which again makes the site much slower. If you need a standalone http2 checker try this HTTP2 Checker at SimpleUptime.co
HTML Download Time (TTFB + time to download HTML): 1.316s
Here we're measuring something we call HTML time. This is essentially your TTFB (time to first byte) AND the time required to download your HTML file combined. Your HTML needs to download before your site will render so the faster this happens the faster the actual AND perceived load time will be for your visitor. We measure this because poor quality or overloaded hosts will cause the HTML download time to be slow. If you're using Wordpress then you pretty much MUST use a caching plugin to get reasonable time on this metric and overall good load time for your site. WP Rocket is an excellent option here and if you're DIY-ing or less technical will usually be the best caching plugin to use. We often find that when people DIY their own speed optimization they blindly follow recommendations from online tools (many of these out of date) and end up generating huge HTML files that take a long time to download so this could be an issue too. The smaller your HTML file the faster it is to download. This article details how to improve your time to first byte and server response times.
HTML File Size: 36.2 KB
Here we're measuring the size of your HTML file. This is really important because the HTML file needs to be both downloaded and parsed in order for your site to render. The smaller your HTML file the faster it'll download, the faster it'll parse and thus the quicker your site will load and be perceived to load to your visitors. Ideally this number should be as low as possible, 50kb-100kb Quite often people blindly follow recommendations from online speed test tools and website audit tools and "inline" CSS and Javascript with the goal of making the site faster. The problem here is that this makes the HTML file HUGE which is something we absolutely want to avoid. How we improve this metric: We recommend you don't inline javascript files as 99% of the time Javascript is best left in separate files. Reducing the number of WordPress plugins and third party apps and tools can also reduce the size of your HTML and CSS. Most of the sites we see at WPSpeedFix.com have plugins and apps installed that are no longer being used and a simple audit identifies what can be removed. HTTP/2 Push on CSS can help speed up CSS and JS files in some cases too.
Number of Javascript Files: 0
Here we count the number of Javascript files your site or page is using. JS is required to do a whole bunch of things on your page and the fewer Javascript files you have the faster your site will feel. Javascript files all make the web browser do "work" which means they use CPU time and often talk to different systems on the internet. The more JS files you have typically the more processing your browser or device needs to do so the slower your page will feel. With this metric fewer is better. *Sometimes* you can improve how fast your site feels by moving your Javascript from the header of your site to the footer which causes it to load later in the loading and render process. Defering or loading Javascript asynchronously can also help minimize it's impact. A simple action step you can take is to analyze the waterfall view below and identify any software or tools you're not actively using and remove those from the website - often marketing and analytics tools were installed years ago and are no longer in use. If you're using WordPress and injecting code using plugins often you can squeeze a little more speed out of your site by implementing Google Tag Manager and using that to fire third party scripts and code.
Number of CSS Files: 0
Here we count the number of CSS files your site or page is using. CSS is required to render the page so the more lightweight and the fewer the number of CSS files you have, the faster your page will feel to visitors. This "feeling" of speed doesn't necessarily show up in speed test tools. CSS files need to load in order for your site to render (display to the visitor). CSS speed impacts a metric called "first contentful paint" or FCP (we don't currently test this). HTTP/2 Push will make a big difference to CSS load speed so important you have that in place.
Number of requests for resources not on the tested domain: 0
In this test we count the number of file requests that are not on the domain or web address you tested. When we look at site speed we typically break the site into two: 1. Your WordPress Core and everything that comes from your hosting 2. Third party files and resources. We have almost 100% control over WordPress and related files so they can almost always be heavily optimized but generally only a small amount of control over third party files and resources. We want to limit third party files and resources as much as possible as typically they're much slower to load than files loading off our WordPress core. Click play on the video below to learn more about this metric:
HTTPS support: yes
Initial server response: 404
Was a CDN or Content Delivery Network Detected?: no
Here we probe for the presence of a CDN or Content Delivery Network. A CDN is a network of servers located around the world that serve up part of your website and files which both takes the load off your primary web server and speeds up your site globally. A CDN is a key component of a fast loading website. Popular CDNs are: Cloudflare MaxCDN KeyCDN Note that this test is often inaccurate so manually check this result. There's thousands of different CDN services so near impossible to keep up to date with them all.
Number of admin_ajax.php requests: 0
This is a Wordpress focused test. Here we count the number of admin_ajax.php requests your page made. Generally these requests can be quite slow and heavy so we want to minimize them where possible.
HTTP/2 Push Detected?: no
HTTP/2 Push is a feature of the HTTP/2 protocol. With HTTP/2 Push in place, files and resources required to render the webpage are automatically sent to the visitor before they even request them. This optimization is a key component of getting that instant, snappy load feeling for people visiting your website. Your web server needs to support HTTP2 in order for this feature to be available. If you're using Wordpress there are several plugins that will add this functionality to your site. This optimization effectively supersedes some older recommendations you'll find around the web for CSS and JS combining and a technique called domain sharding. ***NOTE that if you're using Cloudflare HTTP2 push may not be possible. Custom code can be added to your site to configure Cloudflare with HTTP2 push BUT on many hosts this can cause problems and intermittent "500 Internal Server Error" messages in 1 out of 10 or 20 page loads
Does the Canonical SEO tag match the tested domain?: no
We probe the canonical tag in the web page source code to make sure it matches the tested URL. They should match. If they don't match or this result returns a no then you may be missing the canonical tag or you may be testing the wrong address - for example you're testing https://wpspeedfix.com (missing the WWW) instead of https://www.wpspeedfix.com
Robots.txt support: yes
Does your site support Next-Gen image formats?: no
In this test we probe for Next-Gen images formats (primarily .webp images) You're probably familiar with JPG and PNG images but most people don't realize there are newer, more optimized formats such as .webp Often .webp files will be 50%+ smaller than the equivalent JPG or PNG. Unfortunately not all browsers and devices support Next-Gen image formats so this needs to be done via plugin or a CDN (content delivery network) The guys at Shortpixel provide a tool to test how compress-able your images are. This blog post explains how to inject webp images in Wordpress using their plugin.
Slow Hosting Provider?: no
With this test we probe your hosting provider to see if it's on our slow hosts list. Note that this test is not always accurate as there are thousands of providers across the web. Hosts that are well known across the web to be slow and unreliable include: Bluehost Godaddy Hostgator Site5 1and1 Any host that is part of EIG - Endurance (see EIG Hosts Crazydomains Netregistry Melbourne IT Network Solutions Three fast web hosting companies to consider that have a focus on speed and performance and do have http2 protocol support are: Cloudways - lightning fast, managed, dedicated servers Siteground - a fast general purpose web hosting provider Kinsta - a high speed managed WordPress host If you're looking for country specific recommendations, here's some additional information: The Fastest WordPress hosting Worldwide - a more detailed list of who we recommend, why we recommend them and who they're best suited to The Best WordPress hosting in Australia - a common mistake Australian businesses make is hosting overseas instead of a local provider which means your site is automatically 1-2 seconds slower. The Best & Fastest WordPress hosting in the UK - the UK and Europe are unique in that they often serve a broader geographic area than just a single country. Again a common mistake UK businesses make is hosting in the US which again makes the site much slower.
Lazy loading detected?: no
Lazy loading can significantly speed up your site In this test we're probing for lazy load support. Lazy loading defers the load of files that sit outside the initial viewable area on your website or elements that are "below the fold". This speeds up the initial load of your website as there are less files to load. As the visitor scrolls down the page files and other resources are loaded as the come into view. This optimization is particularly useful on image heavy sites, pages that are really long with a long of images and pages with a lot of embedded content like several Youtube videos. Best Lazy Load plugin for Wordpress If you're using WordPress, two easy ways to implement lazy loading for images, videos and Youtube embeds and iFrames are using either WP Rocket or PerfMatters. We use both WPRocket and PerfMatters but prefer PerfMatters. for lazy loading as it's more Core Web Vitals friendly as it allows us to exclude the first X number of images on the page from lazy loading as we want to avoid lazy loading images (we usually set to 4 or 6 images) above the fold. We strongly recommend excluding your logo image from lazy loading as that will help improve your FCP timing too. Read more about PerfMatters lazy loading features here. For additional information on fixing this error and reducing page sizes see this blog post titled How To Fix The ‘Avoid Enormous Network Payload’ Warning In Google Pagespeed Insights
First CPU Idle: 0.0s
Load Time: 0.0s
Document Complete Requests: 0
Document Complete Bytes in: 0 Bytes
LCP Timing (Render Mostly Finished): 0.0s
Largest Contentful Paint (LCP) is a Google Core Web Vitals metric. It measures when the largest content element in the viewport becomes visible. Broadly you can consider it the render mostly complete. Google considers an LCP under 2.5 seconds to be fast. Over 4 seconds is bad. If this shows a zero there may be an error happening under the bonnet, e.g a 404 or JS error. This article provides a detailed guide on reducing and improving your Largest Contentful Paint timing.
Cumulative Layout Shift (CLS): 0
CLS measures the unexpected layout shift that occurs during the page load. Ideally this should be under 0.1. Scores over 0.25 are considered a poor user experience.
Total Blocking Time (TBT): 0.0s
Time To Download On 1.6mb Internet Connection (slow speed): 0.177s
Time To Download On 10mb Internet Connection (moderate speed): 0.028s
Time To Download On 25mb Internet Connection (faster speed): 0.011s
FCP Timing (Core Web Vitals): 0.0s
First contentful paint or FCP is an important metric as it's the start of the site render and is when the user sees something happening. This timing is the data Google has on the average FCP for this page or the entire site if page level metrics are not available. The data is data pulled directly from Google's Core Web Vitals API. A FAST score here is under 1.8 seconds FCP time encompasses a number of elements and there are many ways to improve this metric including reducing DNS lookup time, reducing TTFB, minimizing or eliminating render blocking CSS and Javascript as well as reducing the weight or filesize of elements “above the fold” on a page by doing things like using Lazy Loading and Nextgen Image Optimization. In most cases your FCP time should be lower than the Fully Loaded Time, if it's not usually the culprit is excessive amounts of javascript causing high CPU usage. This article goes into detail on how to reduce your First Contentful Paint or FCP Timing
LCP Timing (Core Web Vitals): 0.0s
CLS (Core Web Vitals): 0
CLS measures the unexpected layout shift that occurs during the page load. Ideally this should be under 0.1. Scores over 0.25 are considered a poor user experience.
First Input Delay (Core Web Vitals): 0
First Input Delay (FID) measures interactivity or how quickly the site responds to the first user input. Good is under 100ms, 100ms-300ms needs improvement and 300ms+ is not great.

Response Code	Responses
301 Moved Permanently	1
404 Not Found	1

Name: DigitalOcean, LLC

Location: United States

IP address: 134.209.79.134

Nameservers: ns1479.websitewelcome.com, ns1480.websitewelcome.com