Critical CSS is a performance feature that was added. You can enable this in the Options > Performance tab, or when going through the Performance Wizard. Once it has been enabled, you can access the Critical CSS page from the WordPress sidebar at Avada > Critical CSS, or at Maintenance > Critical CSS from the Avada Dashboard.
Both take you to the Critical CSS page, where you can generate Critical CSS for both pages and posts. Critical CSS is the CSS necessary to style the above the fold content. When generated for a page, this will be loaded into the page head, with the rest of the styles moved to the footer, which should mean the above the fold content is quicker to be styled and there is less render blocking time.
On the right hand side of the Critical CSS page, you can select which content you want to generate the Critical CSS for. Options are Homepage, All Pages, Specific Pages, Global Single Post, and Global Single Portfolio. Make your choice, and then click on Generate Critical CSS.
Depending on your choice, and the number of pages or posts etc. you have on your website, this CSS generation may take some time. You will see a dialog as can be seen below, while the CSS is being generated. Do not close the browser during this process, or it will be interrupted.
Once the process has completed, you will see the screen looks something like this, with the pages listed for which Critical CSS has been generated.
When you mouse over the generated CSS, you can see some links underneath each set to help you manage the Critical CSS. You can delete the set entirely, or you can clear or regenerate both the Mobile CSS or the Desktop CSS. There is also a Regenerate button at the far right, which regenerates both.
When critical CSS is generated it also checks for images above the fold which are set to skip lazy load. If any are found, it will save those along with the critical CSS and preload them to speed up load time.
After a major update of Avada, the Critical CSS will be temporarily disabled. This happens automatically, as after Avada has been updated, the old CSS can cause artifacts on your pages. The best way to restore the critical CSS is to regenerate all critical CSS (using bulk actions) and then enable it.
Should the Critical CSS be refreshed after an Avada update?
Yes, it should be regenerated. In bigger updates, a lot of CSS might change, but even in smaller ones, some things can change. As can be seen above, after major updates of Avada, Critical CSS is disabled temporarily for this reason, and users will get a dashboard notice about that, so that they can re-enable and regenerate it.
Should the Avada cache be cleared after generating Critical CSS?
No, it’s not necessary. If a third-party cache plugin is in use, it makes sense to do so. Critical CSS does add a specific style tag to the head tag with the above-the-fold CSS. And moves the rest of the compiled styles to the footer. So, it could be affected by cache plugins.
Having a custom Icon Set with just the icons you need for your site will always be better for page load speed than having to load the various Font Awesome Icon subsets. In the Performance Wizard, we have included a helpful way you can scan your site for the icons it uses, so you can then create a custom Icon Set, you can upload. This would then allow you to turn off the Font Awesome icon subsets, slightly improving your page load speed. Let’s see how to do this.
See the How To Use The Performance Wizard doc for full details of that process, but for our purposes, we just want to look at Step 3 of the Wizard. Here you can use the Find Recommendations button, at the top of the page, to scan your site for all the icons it uses. As you can see in the screenshot below, you will then see a list of all icons used and where they are used.
From Avada > Icons, you can then create a new Custom Icon Set to replace the icons you are using. To start, give the Custom Icon Set a name and click on Create A New Icon Set (or just hit Enter). This takes you to the Edit Icon Set page. Now we have created a Custom Icon Set, we have to populate it. To do this, click on the Icomoon link to open Icomoon in a new tab, where you can generate and download a custom icon set in the form of a zip file.
There are several methods to create a Custom Icon Set In Icomoon. You can load the Font Awesome Icon set and select your icons from there, either manually, or by searching.
But in our circumstances, we are replacing a specific set of used icons with a custom set of the same icons. Please see the How To Upload And Use Custom Icons In Avada doc for more general information on creating Icon sets in Icomoon, but for this task, perhaps the easiest way to recreate the specific icon set is to download them directly from the Performance Wizard and upload them to Icomoon.
To do this, the first step is to download the icons from the Performance Wizard. On the Icons page of the Performance Wizard, you will see the Full List of icons. As you can see from the screenshot below, you can click on this icons to download the svg file.
Once you have downloaded all the icons you need to create your set, you can create a new Empty Set in Icomoon for your custom icons to be uploaded into. This is found from the top menu, as seen below.
Then it is simply a matter of dragging and dropping the downloaded icons into your empty set in Icomoon.
Once you have selected all the icons for your custom set, click the Generate Font button at the bottom of the screen, as seen in the screenshot below.
Before continuing on to click Download, one important thing to note is that every icon pack you upload must have a unique Font Name and CSS Class Prefix before importing into Avada. You can change the Icomoon defaults in the Preferences (via the link next to the Download button, or from the top toolbar) before downloading your custom icon set, as seen below. Once you have done this, click Download.
If you don’t want to use the above method, the alternative is to add the FontAwesome Icon Set into Icomoom from the Icomoon Library, as seen below, and then either manually select, or search for the icons you need for your custom icon set.
Searching in Icomoon however, can give many choices, so you need to know which specific icon you used in your website to know which icon to select. This is why downloading the icons from the Performance Wizard is an easier method.
Whether you need to search, or can just recognize the icons you have used visually, you just need to go through and select the icons you need for your custom set. Once you have selected all the icons you need, you can go to the Generate Font button, as previously.
Once you have generated and downloaded your custom font set, you now need to upload it to your website.
Back on the Edit Icon Set page, you will find a simple upload interface to upload your custom icon set. (There is also a shortcut to this page in any element that has the Icon Picker. Here you will find a Plus button in the top right corner of the Icon Picker, which takes you straight to the Custom Icon page.)
To upload a Custom Icon Set, simply give the Set a name, and then click on the Select File button. Navigate to your icon set (as a zip file) and select it.
Then just click Publish in the right hand side. This will load the Custom Icon set. If you need to update the set later on, there is an Update Custom Icon Set button you can use to reupload the set, as seen below. The icons will now be available through the Icon Picker, in their own tab.
OK, that’s it. You can now return to the Global Options (Advanced > Features) and disable the Font Awesome Icon subsets. As you have a Custom Icon Set, these are now not needed.
To use your new Custom icon Set, head to any element that uses an icon, including the Icon Element. There, you will see any custom icon sets at the top of the icon picker, and you can now just choose the set and select icons from that.
In short, Core Web Vitals is part of an update to Google’s Search Results algorithm, that takes into account various aspects of a user’s page experience when browsing a website. Google defines Core Web Vitals as “a set of real-world, user-centered metrics that quantify key aspects of the user experience.”
As can be seen in the screenshot below, the three Core Web Vitals of Largest Contentful Paint (LCP), First Input Delay (FID), and Cumulative Layout Shift (CLS), are combined with other existing metrics as ‘search signals for page experience’. These page experience signals, in combination with more typical content related signals, will be integrated into Google’s search results algorithm, and help determine your website’s position on the SERPs (Search Engine Results Pages).
In this document, we will look at why this change is important to you, how to measure your website’s performance in these areas, what changes Avada has made to help you with this important update, and what you can >do to improve your website to take advantage of these changes.
Before we look in detail at what Core Web Vitals are, let’s first take a quick look at why they matter. Apart from wanting to provide your users with the best user experience they can have, most website owners see page ranking on Google’s search results as very important.
Mid-June of 2021, Google released a new update to its search results algorithm, which will arguably make UX the second most important ranking factor after content. So, for this reason alone, ensuring your website’s Core Web Vitals are up to speed is essential.
As you can see in the quote below, taken from Google’s Blog, providing a good page experience will not override great, relevant content. Google is now also ranking page experience for its search results, and for pages with similar content, the page experience, and hence the Core Web Vitals, will be much more important for a good search ranking.
Initially, there are three Core Web Vitals. The metrics that makeup Core Web Vitals will evolve over time, but the current set for 2021 focuses on three aspects of the user experience – loading, interactivity, and visual stability – and includes the following metrics (and their respective thresholds):
Largest Contentful Paint: This is the time it takes for a page’s main content to load. An ideal LCP measurement is 2.5 seconds or faster. What Google is asking here is how fast does the largest piece of content in the viewport take to load? On many websites, this is typically a slider or an image, but it can also be text.
First Input Delay: This it the time it takes for a page to become interactive. An ideal measurement is less than 100ms. So the question being asked here is how quickly is the page interactive? To put it another way, when a user clicks on something, a button or a JavaScript event, how fast can the browser begin to process that and produce a result?
Cumulative Layout Shift: This is the amount of unexpected layout shift of visual page content. You have probably experienced a situation where you’ve loaded a page on your mobile phone, and go to click a button, and at the last second it shifts and you hit something else. This is a Cumulative Layout Shift. An ideal measurement is less than 0.1. With this question, Google is asking how quickly is the page stable.
There are numerous tools to use to measure Core Web Vitals. What you use will depend on your experience with Developer Tools. Google has provided a number of tools over the years to measure and report on performance. Some developers are experts at using these tools, while others have found the abundance of both tools and metrics challenging to keep up with.
Site owners should not have to be performance gurus in order to understand the quality of experience they are delivering to their users. The Web Vitals initiative aims to simplify the landscape and help sites focus on the metrics that matter most, the Core Web Vitals.
For each of the above metrics, a good threshold to measure is the 75th percentile of page loads, segmented across mobile and desktop devices. Tools that assess Core Web Vitals compliance consider a page passing if it meets the recommended targets at the 75th percentile for all of the above three metrics.
For more details on the tools Google provides in this area, please see this page: https://web.dev/articles/vitals-tools
This is a complex area, and what to do will depend a lot on your actual content. A good place to start however, is the Avada Performance Wizard. This can be found at Avada > Performance, from the WordPress Dashboard, or from Maintenance > Performance Wizard, from the Avada Dashboard. This should be run once you have completed building your site, and can help you optimize the global option settings that can help with page speed, and indirectly, Core Web Vitals.
You should also consider your above-the-fold content. This has a big impact on your Core Web Vitals results, and improving this content can have a big impact. See the How To Optimize Above The Fold Content For Performance Video for full details on this.
Once your pages are complete, you can also generate Critical CSS (CSS for above the fold content) via the Critical CSS page. This is found at Avada > Critical CSS, from the WordPress sidebar, or Maintenance > Critical CSS from the Avada Dashboard. On this page, you can generate the Critical CSS for the home page, any single page, blog posts, portfolios, or the entire site.
Finally, check out the Avada Optimization Guide for plenty of tips and tricks to help you build sites that are super fast to load.
The Avada Performance Wizard is a step-by-step wizard to help you optimize the performance of your Avada website. it can be found at Avada > Performance from the WordPress Dashboard, or Maintenance > Performance Wizard from the Avada Dashboard. Please read on for more information about how the Wizard can help you, and watch the video below for a visual overview.
This screen is just where you begin the Performance Wizard. At the top of the page, there is a Run PageSpeed Insights buton, which you can use to do a before and after comparison of your page loading times.
There is a reminder that the optimization process should only be run once the website has been completed, and there is a link to the Performance related documentation, and a Let’s Start button. Click that to begin the Performance Wizard.
In this step, you can disable any features you aren’t using, thereby reducing the amount of code loaded. Please be cautious, as disabling a feature you are using will result in broken behaviour until it is enabled again.
As you can see in the screenshot below, the Wizard loads with the current Features as set in the Global Options. At the top of the page, there is a Find Recommendations button, which when clicked will scan your website and offer you recommendations about the various features.
Once, the scan is complete, you will see the Wizard’s recommendations. The green ones mean that the current option is appropriate, the red ones are options which the Wizard recommends be changed, and the blue ones are ones that can’t be automated, and require you to consider the options yourself. The Apply All button, found next to the Find Recommendations button at the top, will apply all the red recommendations. But best practice here is to take your time to go through each of these features and make your changes.
Once you have made your choices, click the Save Changes button at the bottom, before clicking Next Step.
In this step, there are two options relating to Icons. You can choose which Font Awesome icon subsets you want to load, and you can set Font Awesome v4 Compatibility.
If you click the Find Recommendations button, the Wizard scans your website and offers a range of infomation pertaining to the icons used on the site, to help you make your choices. It offers a full list of all the icons used on the site, breaking them down into the individual pages they are used on. (If they are under the Meta column, this means they are not used directly in the content, but are in used in a menu). This list is useful if you want to convert your Font Awesome icons to a single custom icon set to improve your load time. See the How To Replace Font Awesome Icons With A Custom Icon Set documentation for more information on that process.
The recommendations for the two font options let you know which subsets you can turn off, or need on, and in the Font Awesome v4 Compatibility option, the recommendation also lets you know if you have any old v4 icons, which you could then update, so you could turn off v4 compatibility.
Once you have made your changes on this page, click Save Changes, and then Next Step.
In this step, you can check which fonts are being loaded on your website and optimize how those fonts are served. Ensure all families and variants selected here are required. Fewer variants will mean fewer requests and therefore faster loading. This page is split into two sections – the Global Fonts, and the Font Serving Global Options.
Clicking on Find Recommendations checks how many font variants are being used on the site, and makes recommendations about the Font Serving options. There are five font options you can change, depending on your website. They will all affect performance to some degree. For example, you can Preload Key Font Variants for a faster LCP (Largest Contentful Paint) if the LCP on your site is a font. Again, when you are done, click Save Changes and then Next Step.
In this step, you can disable any Design, Layout or Form Elements you aren’t using. When disabled, the Elements will not load and will therefore not be available in the Builder.
There are three buttons at the top of this page. Find Recommendations, Enable All, and Disable All.
Clicking on Find Recommendations scans your website to see which Elements you are using, and deselects all the Elements you are NOT using. If your website is finished, you could then save your changes, thus stopping any unused Elements from loading. Just be aware that you would have to re-enable these Elements to use them at a future time.
In this penultimate step of the Wizard, you can optimize how the CSS and JS assets should be enqueued. These options can have a large impact on the performance of the page load but some of these can also break functionality, particularly if you are using a caching plugin, so be sure to test your site after any changes.
When you are done with your changes, click Save Changes and then Finish Wizard.
This takes you to the FInish page, which clears the site cache and assets. The Wizard also displays how many plugins you have, as these can have a big effect on performance. If you have missed any possible improvements, these will be listed on the right-hand side, next to the Active Plugins.
At the bottom, are some links to specific docs that can help with your understanding of website optimization, and how to perform further optimization, such as optimizing for above-the-fold content, and ensuring that your images are all the right size and optimized as well. Finally, at the top, you can click the Run PageSpeed insights button again, to see how the site has improved.
There are always more things you can to to optimize your site, like choosing faster hosting, running a CDN, installing a caching plugin, further optimize your images and much, much more, but the Performance Wizard is a great first step once you have completed your site, to get it up to speed.
Optimization for page load speed is a very complex area, as so many things affect how fast a page loads. This is from the speed of the server, to the options and settings selected, right through to the type of content and the size of the images added to the page.
We have specific content on How To Use The Performance Wizard, and How To Optimize Above The Fold Content For Performance, but in this document, we offer you more general information, in the form of a wide range of optimzation tips to help when building your content.
Performance Tab – find the ideal option combination (it’s impossible to be prescriptive here, as this is not the same for everybody)
We all want our websites to load quickly, and there are a number of services out there to help us test, evaluate, and fix various issues affecting the loading speed of our pages. In this series of docs, we will be looking at the major players in this area, Google PageSpeed Insights, GTMetrix, Pingdom and WebPageTest, and how they can help you improve the loading speed of your Avada website. Read on!
WebPageTest is a website performance testing site, targeted mainly towards developers. It offers a plethora of website performance testing options, in a freshly revamped interface. Of all the major testing platforms, this one is often considered the best, due to it’s enormous number of options. Let’s dig into the options on offer with this awesome tool.
The Simple Configuration interface is correspondingly simple. You can choose whether to use a Desktop or Mobile configuration, using 3G, 4G, or Cable. By default, the site chooses a 4G Mobile configuration, testing from Virginia, USA. You can also include a repeat view of the site, and run a Lighthouse audit, but that’s where your options stop. For a simple test though, this is still a great starting point.
And not only can you run a Site Performace Test, you can also choose just to run one of the other tests WebPageTest offers, like Core Web Vitals, Lighthouse, Visual Comparison or Traceroute. By default, it runs a Site Performace test which includes the Core Web Vitals anyway.
There are simply too many options in the Advanced Testing section to cover, as this is designed to be a powerful tool for developers. But there are choices here not available in the Simple Testing section that can be very useful, even to beginners.
To start with, there are a huge number of Test Locations to choose from, and in the default location, also a huge variety of devices to use. Virginia is the default location, and with that location, you can choose from a large number of browsers and browser dimensions, which to run your test. If you prefer, you can even select your testing location from a map.
The diversity of testing options on offer make this a very powerful tool for developers. There is the ability to run up to 9 consecutive tests, and you can show results for the first view only or also the repeat views, and you can capturing video of the page load as well. Going into the other tabs would only be useful for developers, but there are a huge range of options to customize your tests as much as you want.
When the test has completed, you are presented with a Performance Summary. This shows your results in all the Observed Metrics, from First Byte though to Total Blocking Time and Total Bytes, as well as Real User Measurments like First Contentful Paint, and Time to First Byte.
At the top of the page content, there is a dropdown menu with the links to the other result tabs. We will cover them one at a time. There is also an option to Re-run the test, and an Export Files link to download the data in various formats.
Let’s now look at the individual results tabs and what they can show us.
The Filmstrip tab offers a filmstrip of the load time of the site. There is a key to understand the individual frames of the filmstrip and you can adjust the Filmstrip Settings.
As you scroll though the filmstrip, a red marker shows you the relevant place in a waterfall diagram. Under this is a chart mapping the visual progress of the site as it loads, and below this are a range of charts showing the Timings, Layout Shifts, Requests and Bytes.
The Details tab is where it gets very technical. As the descriptions says, you can use this page to explore the metric timings and request waterfall for any run of your test. The page is split up into 6 sections: Observed Metrics, Real User Measurements, Waterfall View, Connection View, Request Details, and Request Headers.
The Waterfall View, shows a cascading visualization of the page load across time, and you can click on any individual request to bring up more specific detail about that request. For a developer, you can see how powerful this can be.
The Request Details section provides details of every request, and if you click on the number of any particular one, you will be taken to the corresponding expanded entry in the Request Headers section.
The Web Vitals tab displays the results of the Core Web Vitals, a crucial bunch of metrics, developed by Google. You can read more about them here.
At the bottom of the Results menu are four external links for further analysis. These are Image Analysis, Request Map, Data Cost, and Security Score.
WebPageTest is a highly regarded testing platform, with a toolset mostly suited for developers, or advanced users. There are a profusion of testing locations, and this service gives you all the information you could ever need to optimize your website’s loading time.
Remember, due to hosting and content variables, website optimization is a very complex, technical area, and falls well outside of the support we can provide for Avada.
Apart from our many documentation resources, the Facebook Avada User’s Group has a large and very active membership, and this topic is regularly discussed on the Group.
We all want our websites to load quickly, and there are a number of services out there to help us test, evaluate, and fix various issues affecting the loading speed of our pages. In this series of docs, we will be looking at the major players in this area, Google PageSpeed Insights, GTMetrix, Pingdom and WebPageTest, and how they can help you improve the loading speed of your Avada website. Read on!
GTMetrix is a popular online tool to analyse the load speed and performance of a web page. You can use the service without being logged in, but to take advantage of the full range of free features, you need to sign up for a free account. There is also a different plans, but the free plan is more than enough for the majority of users.
When you visit the site, you are immediately welcomed and invited to get straight to work, with an address bar to input the URL to test. As their website notes “GTmetrix gives you insight on how well your site loads and provides actionable recommendations on how to optimize it.”
If you choose to sign up for a free account and log in, you have many more options to customise your tests, including the browser used, the type of connection, and the location of the tests, which can be very useful if you have a local customer base.
Directly under the URL field, you will find a number of clickable options for that particular test. You can click directly on them to make fast changes to your analysis options.
If you click the Analyse Options on the far right, this will expand to the full options set, where you can choose the following options.
It must be noted that these home page options are for individual tests. If you’d like to set your default options for page analysis, head to your Account, linked at the top right of the site, and make your choices in the following dialog.
Once you have set your options, and entered a URL, you click the Analyse button, and GTmetrix goes to work. When the job is completed, you are presented with a Performance Report. This summarizes your page performance, based off key indicators of page load speed into two areas – the GTmetrix Grade, and Web Vitals.
The individual tabs under the Performance summary area, are where you can see what specific areas your website is performing well, or poorly, in. The Summary Tab provides a Speed Visualisation of your site’s loading time, and below this lists the Top Issues, with the results and recommendations on the individual audits. They are ranked with an impact rating, showing the highest impact issues first. There is a link at the right to see the complete list of structure audits, and you can also see these on the Structure Tab.
Using the small arrow on the far right of each individual audit result, you can expand the section to see more details, as well as links to further information on how to improve the result.
Finally, at the bottom of the Summary Tab, you can see a section called Page Details. This breaks down your page content by bith request type and size. You can hover over a segment to see additional information on that request type so that you can understand if your page is heavy on JavaScript, images, video etc.
The Performance Tab shows the Performance Metrics generated using Lighthouse Performance data, and the Browser Timings, as reported by the browser.
If you mouse over the individual metrics, you can see more information and links to learn more.
The Structure tab shows all meaningful audits, as well as displaying a link to display the No Impact Audits. Just like the Summary tab, you can expand each audit to see more details and to get links to more information.
The Waterfall tab shows a visualization of content loading behavior. It displays the request-by-request loading behavior of your website. Every script, media file, and/or third-party resource your page requests is displayed here.
If you don’t have experience with these charts, they can be overwhelming. Start by reading this How to Read a Waterfall Chart for Beginners document from GTmetrix.
Like the other tabs, you can drill down into the specific load events shown in the Waterfall chart for more information, by clicking on the small plus button at the far left.
It’s also possible in GTmetrix to record and playback a video of the page load, showing yet another visualization of the page load. You can change the speed down to a 1/4 speed to get a good idea of what’s loading when.
Finally, the history tab, shows you your history of tests with that specific url. Depending on how long you have been using it, there will be more or less data in here for you to analyze.
GTmetrix is a relatively easy tool to use, and very valuable to help detect and remedy issues that may be affecting your website’s load time. Much of it is very technical however, and it does however require time, patience and expertise to learn.
Remember, due to hosting and content variables, website optimization is a very complex, technical area, and falls well outside of the support we can provide for Avada.
Apart from our many documentation resources, the Facebook Avada User’s Group has a large and very active membership, and this topic is regularly discussed on the Group.
We all want our websites to load quickly, and there are a number of services out there to help us test, evaluate, and fix various issues affecting the loading speed of our pages. In this series of docs, we will be looking at the major players in this area, Google PageSpeed Insights, GTMetrix, Pingdom and WebPageTest, and how they can help you improve the loading speed of your Avada website. Read on!
Pingdom offers a whole suite of website uptime and performance monitoring tools, but this is a subscription service. However, they also offer the Pingdom Website Speed Test for free. Much like the other testing services, this tool can analyze your website for page loading bottlenecks or other performance issues.
The Pingdom Website Speed Test is a no frills affair, with the only options being the url to test, and the location from which to test. There are 7 locations from which to choose: Tokyo, Frankfurt, London, Washington D.C., San Francisco, Sydney or São Paulo. Simply select one from the drop down menu to choose where to run the test from. Then click Start Test.
When the test has completed you are presented with a Results Summary. This ranks your website url with a grade (based on the YSlow test), lists the total amount of data transferred, the median load time and the total number of requests made. You can also download a HAR file (The HTTP Archive format, or HAR, is a JSON-formatted archive file format for logging of a web browser’s interaction with a site) or share your results via Social Media.
Of all the tests we cover in this series, Pingdom is by far the simplest in terms of results and information. The free service is bare bones, with no documentation. But it is hugely popular, and this is probably because it is the easiest speed testing tool to use! Not everyone is a web performance expert, and so for the typical WordPress user, some of the other alternative tools out there can be quite overwhelming. Sometimes, less is more. Pingdom focuses on the two most important things: how fast your website is and how you can make it faster.
Previously called Performance Insights, and found below the main Results Summary, comes the Improve Page Performance section. This lists individual grades, and a specific score, for the bottom scoring 7 areas that the Pingdom Website Speed Test reports for. Each website may have different suggestions, based on what can be improved.
Next to each suggestion is a drop down arrow which shows further information about that specific issue with suggestions as to how to improve the score.
The next section is the Response Codes. This section lists the response codes, also referred to as HTTP status codes, for the page tested. This can show you if the page is OK, (200), has permanent redirects (301) or links to content that can’t be found (404).
The next sections are the Content Size and the Requests by Content Type and Domain. Each of these is useful to quickly see what is taking up the most resources on your web page, both in terms of size and requests.
This section is a waterfall chart of all the individual requests on your web page. Pingdom’s tests measure TTFB (Time to First Byte). You can sort the waterfall data in many ways, as well as options for changing the order and filtering the information. At the top right, there is Legend, with a color coded system indicating the different stages of a request, and at the left of each request, icons to indicate the different content types of the request. There are also color coded server response codes, showing the various codes. At the bottom of the dialog, you can choose how many entries show per page, which can be useful for sites with a large number of requests.
If you want more details, you can drill down into any specific request to see a whole raft of specific details for that individual requested item.
Pingdom Website Speed test is a relatively basic, but very easy to use, tool to help detect and remedy issues that may be affecting your website’s load time. While not providing as much information as the other analysis tools, it’s simplicity and interface might make it more accessible for beginners.
Remember, due to hosting and content variables, website optimization is a very complex, technical area, and falls well outside of the support we can provide for Avada.
Apart from our many documentation resources, the Facebook Avada User’s Group has a large and very active membership, and this topic is regularly discussed on the Group.
We all want our websites to load quickly, and there are a number of services out there to help us test, evaluate, and fix various issues affecting the loading speed of our pages. In this series of docs, we will be looking at the major players in this area, Google PageSpeed Insights, GTMetrix, Pingdom and WebPageTest, and how they can help you improve the loading speed of your Avada website. Read on!
PageSpeed Insights is an online tool from Google, which helps in identifying performance best practices on any given website. The PageSpeed Insights API (PSI) reports on the performance of a page on both mobile and desktop devices, and provides suggestions on how that page may be improved, and suggests overall ideas of how to make a website faster.
To use PageSpeed Insights, simply enter the url of your website, and click Analyze.
When PageSpeed insights has analyzed your site the results will load on the page. This starts with an assessment of the Core Web Vitals, a collection of metrics that Google consider the most important to real world users. These are the Largest Contentful Paint (LCP), the First input Delay (FID), and the Cumulative Layout Shift (CLS).
Under these other notable metrics are also reported such as First Contentful Paint (FCP), Interaction To Next Paint (INP), and Time To First Byte (TTFB). You can see these results for both Mobile and Desktop. You will notice that the report defaults to the Mobile Results, in line with Google’s Mobile First Indexing. See the Desktop results by clicking on the Desktop link.
There Is also an Expand View link to get more detail for these metrics. PSI classifies the quality of user experiences into three buckets: Good, Needs Improvement, or Poor. Your users experiences are distributed aloing the line, which is also marked with the 75th percentile for that metric.
Just to clarify how to read these figures. If we look at the image below, we can see that 76% of page loads got a good result with the Largest Contentful Paint, a full 99% for the First Input Delay, and 89% for the Cumulative Layout Shift. To pass the Core Web Vitals Assessment, you need the percentage of page loads in the Good section to be at or above the 75th percentile.
To read more about how Google defines the Core Web Vital metrics threshholds, see the following page. You can also read more about this in the PageSpeed Insight Docs.
PageSpeed Insights then provides a score which summarizes the page’s performance. This score is determined by running Lighthouselab data about the page. A score of 90 or above is considered fast, and 50 to 89 is considered average. Below 50 is considered to be slow.
Below this Performance Summary are several sections, that first show the data captured, then a range of audits that show how to fix issues, how to generally improve the site, and finally a list of passed audits. Let’s have a closer look.
Again, the Metrics section has a collapsed or expanded view. The expanded view has a description of the individual metric and a link to learn more about each one.
Below this, the test meta data is displayed, as well as a link to view a Treemap fo the pageload, a timeline view of the page load, and an audit filter. You can show all audits, or just audits relevant to a particular metric. Then come the individual audits.
PSI separates its audits into three sections:
The Opportunities section is what it says on the label. This section provides developers with recommendations to improve a page’s speed and gives an estimation of the page speed gained. You can expand on the opportunities by clicking the small chevron on the right, and there is a link more more information about the particular issue.
Google PageSpeed Insights is a valuable tool to help detect and remedy issues that may be affecting your websites’ load time. It does however require time, patience and expertise. There are also other similar services like GTMetrix, Pingdom, and WebPagetest.
Remember, due to hosting and content variables, site optimization is a very complex area, and falls well outside of the support we can provide for Avada.
The Facebook Avada User’s Group has a large and very active membership, and this topic is regularly discussed on the Group.
Caching and minification is important in any website. Whenever a user visits your site, a lot of information is requested, such as images, styling, as well as retrieving your content from the WordPress database. These factors, plus the amount of visitors you have, can significantly affect your site’s total page loading time. Caching plugins help reduce this by showing your viewers a static version of your site.
Below is a list of our recommended cache plugins to optimize your site’s speed. These plugins have been tested with Avada, and we find that they work well with it. However, please note that these plugins interact differently with different server setups. Please note, we do cannot provide support for any issues caused by third party plugins.
One of our recommended plugins, the PWA plugin, also is well worth a look, when trying to speed up the loading of your site using plugins. What PWA does is to provide a range of different caching strategies, based on your site and the frequency of content updates.