You have a page title and it does not exceed 70 characters. Well done!
About this SEO factor:
Title is the heading of the webpage. The sentence or string enclosed between html title tag () is the title of your website. Search engines searches for the title of your website and displays title along with your website address on search result. Title is the most important element for both SEO and social sharing. Title should be less than 50 to 60 characters because search engine typically displays this length of string or sentence on search result. A good title can consist the primary keyword, secondary keyword and brand name. For example a fictitious gaming information providing sites title may be like "the future of gaming information is here". A webpage title should contain a proper glimpse of the website. title is important element as an identification of your website for user experience, SEO and social sharing. So have a nice and catching title. Learn more
Description is the full interpretation of your website content and features. Most often it is a short paragraph that describe what are features and information provided by the website to its visitors. You may consider it a advertising of your website. Although not important for search engine ranking but very important for hits or visits through search engine results. Description should be less than 150 character because search engine shows this length of paragraph on search result. And every page of website should contain an unique description to avoid description duplication. Description is the definition of your website for user experience so form it as complete but short and precise illustration of your website.
Meta keywords are keywords inside Meta tags. Meta keywords are not likely to be used for search engine ranking. the words of title and description can be used as meta keywords. it is a good idea for SEO other than search engine ranking.
The most using keywords do not match with meta keywords.
About this SEO factor:
Keyword usage is the using of your keywords inside Meta tags and contents of your website. Use keywords that describes your site properly for precise search engine result of your website.
Unique words are uncommon words that reflects your site features and informations. Search engine metrics are not intended to use unique words as ranking factor but it is still useful to get a proper picture of your site contents. Using positive unique words like complete, perfect, shiny, is a good idea user experience.
Stop words are common words like all the preposition, some generic words like download, click me, offer, win etc. since most used keyword may be a slight factor for visitors you are encouraged to use more unique words and less stop words.
The ideal page's ratio of text to HTML code must be lie between 20 to 60%. Because if it is come less than 20% it means you need to write more text in your web page while in case of more than 60% your page might be considered as spam.
1 status is the existence of any content inside h1 tag. Although not important like Meta titles and descriptions for search engine ranking but still a good way to describe your contents in search engine result.
h2 status less important but should be used for proper understanding of your website for visitor.
# If the Joomla site is installed within a folder
# eg www.example.com/joomla/ then the robots.txt file
# MUST be moved to the site root
# eg www.example.com/robots.txt
# AND the joomla folder name MUST be prefixed to all of the
# paths.
# eg the Disallow rule for the /administrator/ folder MUST
# be changed to read
# Disallow: /joomla/administrator/
#
# For more information about the robots.txt standard, see:
# https://www.robotstxt.org/orig.html
User-agent: *
Allow: /*.js*
Allow: /*.css*
Allow: /*.png*
Allow: /*.jpg*
Allow: /*.gif*
Disallow: /administrator/
Disallow: /bin/
Disallow: /cache/
Disallow: /cli/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /layouts/
Disallow: /libraries/
Disallow: /logs/
Disallow: /tmp/
# JSitemap entries
Sitemap: https://www.liquidpurple.com/index.php?option=com_jmap&view=sitemap&format=xml
About this SEO factor:
robots.txt is text file that reside on website root directory and contains the instruction for various robots (mainly search engine robots) for how to crawl and indexing your website for their webpage. robots.txt contains the search bots or others bots name, directory list allowed or disallowed to be indexing and crawling for bots, time delay for bots to crawl and indexing and even the sitemap url. A full access or a full restriction or customized access or restriction can be imposed through robots.txt.
robots.txt is very important for SEO. Your website directories will be crawled and indexed on search engine according to robots.txt instructions. So add a robots.txt file in your website root directory. Write it properly including your content enriched pages and other public pages and exclude any pages which contain sensitive information. Remember robots.txt instruction to restrict access to your sensitive information of your page is not formidable on web page security ground. So do not use it on security purpose. Learn more
Sitemap is a xml file which contain full list of your website urls. It is used to include directories of your websites for crawling and indexing for search engine and access for users. it can help search engine robots for indexing your website more fast and deeply. It is roughly an opposite of robots.txt, You can create a sitemap.xml by various free and paid service or you can write it with proper way (read about how write a sitemap).
Also keep these things in mind:
1) Sitemap must be less than 10 MB (10,485,760 bytes) and can contain maximum 50,000 urls. if you have more uls than this create multiple sitemap files and use a sitemap index file.
2) Put your sitemap in website root directory and add the url of your sitemap in robots.txt.
3) sitemap.xml can be compressed using grip for faster loading.
Broken link: a broken link is an inaccessible link or url of a website. a higher rate of broken links have a negative effect on search engine ranking due to reduced link equity. it also has a bad impact on user experience. There are several reasons for broken link. All are listed below.
1) An incorrect link entered by you.
2) The destination website removed the linked web page given by you. (A common 404 error).
3) The destination website is irreversibly moved or not exists anymore. (Changing domain or site blocked or dysfunctional).
4) User may behind some firewall or alike software or security mechanism that is blocking the access to the destination website.
5) You have provided a link to a site that is blocked by firewall or alike software for outside access. Learn more or Learn more
NoIndex : noindex directive is a meta tag value. noindex directive is for not to show your website on search engine results. You must not set ‘noindex’ as value in meta tags if you want to be your website on search engine result.
By default, a webpage is set to “index.” You should add a <meta name="robots" content="noindex" /> directive to a webpage in the <head> section of the HTML if you do not want search engines to crawl a given page and include it in the SERPs (Search Engine Results Pages).
DoFollow & NoFollow : nofollow directive is a meta tag value. Nofollow directive is for not to follow any links of your website by search engine bots. You must not set ‘nofollow’ as value in meta tags if you want follow your link by search engine bots.
By default, links are set to “follow.” You would set a link to “nofollow” in this way: <a href="http://www.example.com/" rel="nofollow">Anchor Text</a> if you want to suggest to Google that the hyperlink should not pass any link equity/SEO value to the link target.
An SEO friendly link is roughly follows these rules. The url should contain dash as a separator, not to contain parameters and numbers and should be static urls.
To resolve this use these techniques.
1) Replace underscore or other separator by dash, clean url by deleting or replaceing number and parameters.
2) Marge your www and non www urls.
3) Do not use dynamic and related urls. Create an xml sitemap for proper indexing of search engine.
4) Block unfriendly and irrelevant links through robots.txt.
5) Endorse your canonical urls in canonical tag. Learn more
An alternate title for image. Alt attribute content to describe an image. It is necessary for notifying search engine spider and improve actability to your website. So put a suitable title for your image at least those are your website content not including the images for designing your website. To resolve this put a suitable title in your alt attributes. Learn more
Older HTML tags and attributes that have been superseded by other more functional or flexible alternatives (whether as HTML or as CSS ) are declared as deprecated in HTML4 by the W3C - the consortium that sets the HTML standards. Browsers should continue to support deprecated tags and attributes, but eventually these tags are likely to become obsolete and so future support cannot be guaranteed.
HTML page size is the one of the main factors of webpage loading time. It should be less than 100 KB according to google recommendation. Note that, this size not including external css, js or images files. So small page size less loading time.
To reduce your page size do this steps
1) Move all your css and js code to external file.
2) make sure your text content be on top of the page so that it can displayed before full page loading.
3) Reduce or compress all the image, flash media file etc. will be better if these files are less than 100 KB Learn more
GZIP is a generic compressor that can be applied to any stream of bytes: under the hood it remembers some of the previously seen content and attempts to find and replace duplicate data fragments in an efficient way - for the curious, great low-level explanation of GZIP. However, in practice, GZIP performs best on text-based content, often achieving compression rates of as high as 70-90% for larger files, whereas running GZIP on assets that are already compressed via alternative algorithms (e.g. most image formats) yields little to no improvement. It is also recommended that, GZIP compressed size should be <=33 KB
Inline css is the css code reside in html page under html tags not in external .css file. Inline css increases the loading time of your webpage which is an important search engine ranking factor. So try not to use inline css.
Internal css is the css codes which resides on html page inside style tag. Internal css is increases loading time since no page caching is possible for internal css. Try to put your css code in external file.
Micro data is the information underlying a html string or paragraph. Consider a string “Avatar”, it could refer a profile picture on forum, blog or social networking site or may it refer to a highly successful 3D movie. Microdot is used to specify the reference or underlying information about an html string. Microdata gives chances to search engine and other application for better understanding of your content and better display significantly on search result. Learn more
If multiple domain name is registered under single ip address the search bots can label other sites as duplicates of one sites. This is ip canonicalization. Little bit like url canonicalizaion. To solve this use redirects. Learn more
Canonical tags make your all urls those lead to a single address or webpage into a single url. Like : <link rel="canonical" href="https://mywebsite.com/home" /> <link rel="canonical" href="https://www.mywebsite.com/home" />
Both refer to the link mywebsite.com/home. So all the different url with same content or page now comes under the link or url mywebsite.com/home. Which will boost up your search engine ranking by eliminating content duplication.
Use canonical tag for all the same urls. Learn more
Site failed plain text email test.1plain text email found.
Plain Text Email List
Sales@LiquidPurple.com
About this SEO factor:
Plain text email address is vulnerable to email scrapping agents. An email scrapping agent crawls your website and collects every Email address which written in plain text. So existence of plain text email address in your website can help spammers in email Harvesting. This could be a bad sign for search engine.
To fight this you can obfuscate your email addresses in several ways:
1) CSS pseudo classes.
2) Writing backward your email address.
3) Turn of display using css.
4) Obfuscate your email address using javascript.
5) Using wordpress and php (wordpress site only). Learn more
MOBILE
Third-party code blocked the main thread for 10 ms
DESKTOP
Third-party code blocked the main thread for 0 ms
Your third-party code only takes 0.01 seconds. Not terrible.
About this SEO factor:
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn More
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn More
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn More
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn More
Your site uses video formats for animated content.
About this SEO factor:
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn More
Your webiste does not have discernible name for Links.
About this SEO factor:
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn More
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn More
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn More
`[aria-hidden="true"]` elements do not contain focusable descendents
About this SEO factor:
Focusable descendents within an aria-hidden=true element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
`button`, `link`, and `menuitem` elements have accessible names
About this SEO factor:
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
About this SEO factor:
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn More
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
No element has a `[tabindex]` value greater than 0
About this SEO factor:
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
AVOIDS requesting the geolocation permission on page load.
About this SEO factor:
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn More
The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the pagehide or visibilitychange events instead. Learn More
AVOIDS requesting the notification permission on page load.
About this SEO factor:
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn More
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn More
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
A character encoding declaration is required. It can be done with a tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn More
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn More
Templates, extensions, and server specifications all contribute to server response time. Consider finding a more optimized template, carefully selecting an optimization extension, and/or upgrading your server.
uses-long-cache-ttl
Read about [Browser Caching in Joomla].
uses-text-compression
You can enable text compression by enabling Gzip Page Compression in Joomla .
uses-optimized-images
Consider using an [image optimization plugin] that compresses your images while retaining quality.
efficient-animated-content
Consider uploading your GIF to a service which will make it available to embed as an HTML5 video.
render-blocking-resources
There are a number of Joomla plugins that can help you [inline critical assets] or [defer less important resources]. Beware that optimizations provided by these plugins may break features of your templates or plugins, so you will need to test these thoroughly.
uses-responsive-images
Consider using a [responsive images plugin] to use responsive images in your content.
unused-css-rules
Consider reducing, or switching, the number of [Joomla extensions] loading unused CSS in your page. To identify extensions that are adding extraneous CSS, try running [code coverage] in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the stylesheet. Look out for plugins that have many stylesheets in the list which have a lot of red in code coverage. A plugin should only enqueue a stylesheet if it is actually used on the page.
unminified-css
A number of [Joomla extensions] can speed up your site by concatenating, minifying, and compressing your css styles. There are also templates that provide this functionality.
unminified-javascript
A number of [Joomla extensions] can speed up your site by concatenating, minifying, and compressing your scripts. There are also templates that provide this functionality.
unused-javascript
Consider reducing, or switching, the number of [Joomla extensions] loading unused JavaScript in your page. To identify plugins that are adding extraneous JS, try running [code coverage] in Chrome DevTools. You can identify the extension responsible from the URL of the script. Look out for extensions that have many scripts in the list which have a lot of red in code coverage. An extension should only enqueue a script if it is actually used on the page.
total-byte-weight
Consider showing excerpts in your article categories , reducing the number of articles shown on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.
modern-image-formats
Consider using a [plugin] or service that will automatically convert your uploaded images to the optimal formats.
offscreen-images
Install a [lazy-load Joomla plugin] that provides the ability to defer any offscreen images, or switch to a template that provides that functionality. Starting with Joomla 4.0, all new images will [automatically] get the `loading` attribute from the core.
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn More
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn More
`[aria-hidden="true"]` elements do not contain focusable descendents
About this SEO factor:
Focusable descendents within an aria-hidden=true element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
`button`, `link`, and `menuitem` elements have accessible names
About this SEO factor:
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
About this SEO factor:
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn More
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
No element has a `[tabindex]` value greater than 0
About this SEO factor:
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed contentLearn More, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn More
AVOIDS requesting the geolocation permission on page load.
About this SEO factor:
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn More
The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the pagehide or visibilitychange events instead. Learn More
NO issues in the `Issues` panel in Chrome Devtools.
About this SEO factor:
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn More
Third-party code blocked the main thread for 10 ms
Wasted Miliseconds: 11.42
Wasted Bytes: 81645
Add a <meta name="viewport"> tag to optimize your app for mobile screens. not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn More
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn More
ID
Label
Selector
More:
Element does not have an alt attribute
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
Element's default semantics were not overridden with role="none" or role="presentation"
Font sizes less than 12px are too small to be legible and require mobile visitors to pinch to zoom in order to read. Strive to have > 60% of page text at least 12px. Learn More
All tap targets ARE sized appropriately. 100% appropriately sized tap targets
About this SEO factor:
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn More
This is a screengrab of what this page looks like on desktop computers.
3 6-21-A
4 6-36-A
6 6-11-A
7 6-102-EM
8 6-41-A
9 6-114-DIV
10 6-28-A
11 6-106-DIV
12 6-22-A
15 6-54-A
16 6-46-A
17 6-31-A
18 6-113-DIV
19 6-45-A
21 6-100-DIV
22 6-103-P
24 6-57-A
25 6-95-DIV
26 6-9-A
27 6-59-A
28 6-0-A
29 6-27-A
34 6-32-A
35 6-5-A
38 6-101-EM
41 6-58-A
42 6-38-A
43 6-104-EM
46 6-53-A
47 6-118-INPUT
48 6-99-P
49 6-55-A
50 6-91-INPUT
51 6-52-A
52 6-3-A
53 6-34-A
54 6-7-A
55 6-92-BUTTON
56 6-1-A
58 6-56-A
61 6-30-A
62 6-112-SPAN
65 6-4-A
67 6-40-A
68 6-107-DIV
69 6-39-A
71 6-33-A
72 6-105-P
76 6-37-A
79 6-42-A
81 6-2-A
82 6-10-A
83 6-43-A
84 6-108-DIV
85 6-115-FOOTER
87 6-51-A
90 6-117-STRONG
91 6-109-DIV
93 6-111-DIV
94 6-110-DIV
95 6-96-DIV
98 6-20-A
100 6-97-BUTTON
101 6-35-A
102 6-60-A
106 6-8-A
107 6-6-A
108 6-29-A
111 6-116-EM
112 6-94-SELECT
113 6-98-BUTTON
115 6-44-A
118 6-93-SELECT
Performance Metrics
The following metrics are generated using performance data.
Overall Performance Score:
0.86
First Contentful Paint
First Contentful Paint marks the time at which the first text or image is painted onto your page. A good user experience is 0.9s or less.
6.2 s DESKTOP
1.2 s Score: 0.77Learn More
OK, but consider improvement
1.2s
Time to Interactive
Time to interactive is the amount of time it takes for the page to become fully interactive. A good user experience is 2.5s or less.
7.6 s DESKTOP
1.7 s Learn More
Excellent!
1.7s
Speed Index
Speed Index shows how quickly the contents of a page are visibly populated. A good user experience is 1.3s or less.
6.2 s DESKTOP
2.3 s Score: 0.51Learn More
Much more than recommended
2.3s
Total Blocking Time
How much time is blocked by scripts during your page loading process or the sum of all time periods between FCP and Time to Interactive. A good user experience is 150ms or less. Learn More
Excellent!
60ms
Largest Contentful Paint
Largest Contentful Paint marks how long it takes for the largest element of content (e.g. a hero image) to be painted on your page. A good user experience is 1.2s or less. Learn more.
Longer than recommended
1.7s
Cumulative Layout Shift
Cumulative Layout Shift measures the movement of visible elements within the viewport or how much your page's layout shifts as it loads. A good user experience is a score of 0.1 or less. Learn More
Excellent!
0.007
Total Page Size - 1.6 MB
IMG 483.2 KB
Images
483.2 KB Size29.01% of Total Page Size
JS 464.3 KB
JavaScript
464.3 KB Size27.88% of Total Page Size
Font 395.0 KB
Fonts
395.0 KB Size23.71% of Total Page Size
CSS 193.4 KB
CSS Stylesheets
193.4 KB Size11.61% of Total Page Size
HTML 128.1 KB
HTML
128.1 KB Size7.69% of Total Page Size
Other
1.5 KB Size0.09% of Total Page Size
Media
0 B Size0.00% of Total Page Size
Total Page Requests - 98
IMG 20.41%
Images
20 Requests20.41% of Total Page Requests
JS 42.86%
JavaScript
42 Requests42.86% of Total Page Requests
Font 7.14%
Fonts
7 Requests7.14% of Total Page Requests
CSS 24.49%
CSS Stylesheets
24 Requests24.49% of Total Page Requests
HTML 1.02%
HTML
1 Requests1.02% of Total Page Requests
Other 4.08%
Other
4 Requests4.08% of Total Page Requests
Video 0.00%
Media
0 Requests0.00% of Total Page Requests
HTML
JS
CSS
IMG
Video
Font
Other
Response Codes:
Response Code
Responses
200
102
-1
1
Lab Data
First Meaningful Paint
6.2 s
DESKTOP
1.5 s
ID:
first-meaningful-paint
Title:
First Meaningful Paint
Description:
First Meaningful Paint measures when the primary content of a page is visible. [Learn more](https://web.dev/first-meaningful-paint/).
Score:
0.59
Score Display Mode:
numeric
Display Value:
1.5 s
Numeric Value:
1450
Max Potential First Input Delay
360 ms
DESKTOP
130 ms
Audits - Max-Potential FID
ID:
max-potential-fid
Title:
Max Potential First Input Delay
Description:
The maximum potential First Input Delay that your users could experience is the duration of the longest task. [Learn more](https://web.dev/lighthouse-max-potential-fid/).
Score:
0.9
Score Display Mode:
numeric
Display Value:
130 ms
Numeric Value:
130
Audits - Uses Long Cache TTL
Serve static assets with an efficient cache policy
A long cache lifetime can speed up repeat visits to your page. Learn more
Score:
0.3
89 resources found
SI (Speed Index) MS 15%:
2270
LCP (Largest Contentful Paint) MS 25%:
1710
TTI (Time to Interactive) MS 15%:
1687
TBT (Total Blocking Time) MS 25%:
61
CLS (Cumulative Layout Shift) MS 5%:
0.0068
ID:
third-party-summary
Title:
Minimize third-party usage
Description:
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. [Learn more](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/).
Score:
1
Score Display Mode:
binary
Display Value:
Third-party code blocked the main thread for 0 ms
Item Detail: Text: Google Tag Manager URL: https://marketingplatform.google.com/about/tag-manager/ Type: link Main Thread Time: 22.84 Transfer Size: 42639 Blocking Time: 0 Item Detail: Text: Google Analytics URL: https://marketingplatform.google.com/about/analytics/ Type: link Main Thread Time: 33.526 Transfer Size: 21249 Blocking Time: 0 Item Detail: Text: FontAwesome CDN URL: https://fontawesome.com/ Type: link Main Thread Time: 3.657 Transfer Size: 12915 Blocking Time: 0 Item Detail: Text: Cloudflare CDN URL: https://cdnjs.com/ Type: link Main Thread Time: 20.106 Transfer Size: 3468 Blocking Time: 0 Item Detail: Text: Google/Doubleclick Ads URL: https://marketingplatform.google.com/about/enterprise/ Type: link Main Thread Time: 0 Transfer Size: 692 Blocking Time: 0 Item Detail: Text: Other Google APIs/SDKs URL: https://developers.google.com/apis-explorer/#p/ Type: link Main Thread Time: 0 Transfer Size: 673 Blocking Time: 0
Type:
table
Wasted Bytes:
81636
Wasted Time (ms):
0
Text:
Third-Party
Item Type:
link
Key:
entity
Key:
transferSize
Text:
Transfer Size
Granularity:
1
Item Type:
bytes
Key:
blockingTime
Text:
Main-Thread Blocking Time
Granularity:
1
Item Type:
ms
Audits - Timing Budget
ID:
timing-budget
Title:
Timing budget
Description:
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. [Learn more](https://developers.google.com/web/tools/lighthouse/audits/budgets).
Score:
Unknown
Score Display Mode:
notApplicable
Audits - Render Blocking Resources
ID:
render-blocking-resources
Title:
Eliminate render-blocking resources
Description:
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn more](https://web.dev/render-blocking-resources/).
Score:
0.5
Score Display Mode:
numeric
Display Value:
Potential savings of 770 ms
Numeric Value:
772
Type:
opportunity
Overall Savings (ms):
772
Audits - Render Blocking Resources - Details
Data item: Total Bytes: 22607 URL: https://www.liquidpurple.com/templates/purity_iii/css/bootstrap.css Wasted Time (ms): 80 Data item: Total Bytes: 12915 URL: https://use.fontawesome.com/releases/v5.8.2/css/all.css Wasted Time (ms): 230 Data item: Total Bytes: 3468 URL: https://cdnjs.cloudflare.com/ajax/libs/wow/1.1.2/wow.min.js Wasted Time (ms): 230 Data item: Total Bytes: 81042 URL: https://www.liquidpurple.com/media/com_payplans/scripts/site-5.0.3.min.js Wasted Time (ms): 80
Audits - Render Blocking Resources - Headings
Heading Item: Label: URL Value Type: url Key: url Heading Item: Label: Transfer Size Value Type: bytes Key: totalBytes Heading Item: Label: Potential Savings Value Type: timespanMs Key: wastedMs
Audits - Main Thread Tasks
ID:
main-thread-tasks
Title:
Tasks
Description:
Lists the toplevel main thread tasks that executed during page load.
Score:
Unknown
Score Display Mode:
informative
Type:
table
Audits - Main Thread Tasks - Headings
Heading Items: Text: Start Time Key: startTime Item Type: ms Granularity: 1 Heading Items: Text: End Time Key: duration Item Type: ms Granularity: 1
Audits - Network RTT
ID:
network-rtt
Title:
Network Round Trip Times
Description:
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. [Learn more](https://hpbn.co/primer-on-latency-and-bandwidth/).
Score:
Unknown
Score Display Mode:
informative
Display Value:
0 ms
Numeric Value:
0
ID:
interactive
Title:
Time to Interactive
Description:
Time to interactive is the amount of time it takes for the page to become fully interactive. [Learn more](https://web.dev/interactive/).
Score:
0.98
Score Display Mode:
numeric
Display Value:
1.7 s
Numeric Value:
1687
Audits - Critical Request Chains
ID:
critical-request-chains
Title:
Avoid chaining critical requests
Description:
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. [Learn more](https://web.dev/critical-request-chains/).
Score:
Unknown
Score Display Mode:
informative
Display Value:
59 chains found
Longest Chain Transfer Size:
17914
Longest Chain Duration:
2771.7039999989
Longest Chain Length:
3
Type:
criticalrequestchain
Audits - Critical Request Chains - Details
Critical Request Chains Request: Request Start Time: 50011.697276 Request Response Received Time: 50013.850595 Request End Time: 50013.850602 Request URL: https://www.liquidpurple.com/ Request Transfer Size: 131191 Critical Request Chains Children: Critical Request Chains Child: request startTime: 50013.867435 Request Response Received Time: 50014.023043 Request End Time: 50014.023045 Request URL: https://www.liquidpurple.com/components/com_seofront/assets/js/custom.js Request Transfer Size: 356 Critical Request Chains Child: request startTime: 50013.866885 Request Response Received Time: 50013.97124 Request End Time: 50013.971245 Request URL: https://www.liquidpurple.com/components/com_seofront/assets/plugins/jquery.appear.js Request Transfer Size: 1765 Critical Request Chains Child: request startTime: 50013.870104 Request Response Received Time: 50013.954308 Request End Time: 50013.954311 Request URL: https://www.liquidpurple.com/plugins/system/t3/base-bs3/js/menu.js Request Transfer Size: 4665 Critical Request Chains Child: request startTime: 50013.870436 Request Response Received Time: 50013.951421 Request End Time: 50013.951424 Request URL: https://www.liquidpurple.com/plugins/system/t3/base-bs3/js/nav-collapse.js Request Transfer Size: 1847 Critical Request Chains Child: request startTime: 50013.864391 Request Response Received Time: 50013.957739 Request End Time: 50013.957743 Request URL: https://www.liquidpurple.com/media/com_joomtestimonials/css/swiper.min.css Request Transfer Size: 3472 Critical Request Chains Child: request startTime: 50013.86317 Request Response Received Time: 50013.975747 Request End Time: 50013.97575 Request URL: https://www.liquidpurple.com/components/com_seoglossary/assets/css/jqeasytooltip.css Request Transfer Size: 4276 Critical Request Chains Child: request startTime: 50013.873851 Request Response Received Time: 50013.950299 Request End Time: 50013.950309 Request URL: https://www.liquidpurple.com/components/com_roksprocket/layouts/features/assets/js/features.js Request Transfer Size: 3020 Critical Request Chains Child: request startTime: 50013.866577 Request Response Received Time: 50013.996799 Request End Time: 50013.996802 Request URL: https://www.liquidpurple.com/components/com_seofront/assets/plugins/ms-dropdown/js/jquery.dd.js Request Transfer Size: 13167 Critical Request Chains Child: request startTime: 50013.871963 Request Response Received Time: 50013.960085 Request End Time: 50013.960089 Request URL: https://www.liquidpurple.com/components/com_roksprocket/assets/js/moofx.js Request Transfer Size: 14907 Critical Request Chains Child: request startTime: 50013.864015 Request Response Received Time: 50014.024689 Request End Time: 50014.024691 Request URL: https://www.liquidpurple.com/media/com_joomtestimonials/css/bootstrapfix.css Request Transfer Size: 1116 Critical Request Chains Child: request startTime: 50013.873481 Request Response Received Time: 50013.888498 Request End Time: 50013.888504 Request URL: https://cdnjs.cloudflare.com/ajax/libs/wow/1.1.2/wow.min.js Request Transfer Size: 3468 Critical Request Chains Child: request startTime: 50013.870875 Request Response Received Time: 50013.975428 Request End Time: 50013.975431 Request URL: https://www.liquidpurple.com/components/com_seoglossary/assets/js/jqeasytooltip.v1.3.js Request Transfer Size: 6544 Critical Request Chains Child: request startTime: 50013.867735 Request Response Received Time: 50013.996257 Request End Time: 50013.996263 Request URL: https://www.liquidpurple.com/components/com_seofront/assets/js/isotope.pkgd.js Request Transfer Size: 22771 Critical Request Chains Child: request startTime: 50013.871486 Request Response Received Time: 50014.027052 Request End Time: 50014.027068 Request URL: https://www.liquidpurple.com/components/com_roksprocket/assets/js/rokmediaqueries.js Request Transfer Size: 2109 Critical Request Chains Child: request startTime: 50013.862103 Request Response Received Time: 50014.003393 Request End Time: 50014.0034 Request URL: https://www.liquidpurple.com/templates/purity_iii/css/megamenu.css Request Transfer Size: 2324 Critical Request Chains Child: request startTime: 50013.866997 Request Response Received Time: 50014.024253 Request End Time: 50014.024255 Request URL: https://www.liquidpurple.com/components/com_seofront/assets/js/template.js Request Transfer Size: 1642 Critical Request Chains Child: request startTime: 50013.866238 Request Response Received Time: 50014.022338 Request End Time: 50014.022346 Request URL: https://www.liquidpurple.com/components/com_seofront/assets/plugins/jquery.min.js Request Transfer Size: 34171 Critical Request Chains Child: request startTime: 50013.86149 Request Response Received Time: 50013.952491 Request End Time: 50013.952494 Request URL: https://www.liquidpurple.com/templates/system/css/system.css Request Transfer Size: 796 Critical Request Chains Child: request startTime: 50013.86064 Request Response Received Time: 50014.005291 Request End Time: 50014.005295 Request URL: https://www.liquidpurple.com/templates/purity_iii/css/bootstrap.css Request Transfer Size: 22607 Critical Request Chains Child: request startTime: 50013.873934 Request Response Received Time: 50013.975047 Request End Time: 50013.975051 Request URL: https://www.liquidpurple.com/components/com_roksprocket/layouts/features/themes/showcase/showcase.js Request Transfer Size: 1302 Critical Request Chains Child: request startTime: 50013.863804 Request Response Received Time: 50013.953476 Request End Time: 50013.953481 Request URL: https://www.liquidpurple.com/media/com_joomtestimonials/css/bootstrap.css Request Transfer Size: 27208 Critical Request Chains Child: request startTime: 50013.864719 Request Response Received Time: 50014.009713 Request End Time: 50014.009716 Request URL: https://www.liquidpurple.com/components/com_roksprocket/layouts/features/themes/showcase/showcase.css Request Transfer Size: 1129 Critical Request Chains Child: request startTime: 50013.868484 Request Response Received Time: 50014.025885 Request End Time: 50014.025888 Request URL: https://www.liquidpurple.com/media/jui/js/jquery.min.js?3efd14aada41c7ec345fd8f917dd4257 Request Transfer Size: 35043 Critical Request Chains Child: request startTime: 50013.865239 Request Response Received Time: 50013.997905 Request End Time: 50013.997908 Request URL: https://www.liquidpurple.com/media/com_payplans/themes/site/css/style.min.css?18313f04cea0e078412a028c5361bd4e=1 Request Transfer Size: 4605 Critical Request Chains Child: request startTime: 50013.863433 Request Response Received Time: 50014.026697 Request End Time: 50014.026703 Request URL: https://www.liquidpurple.com/components/com_roksprocket/layouts/strips/themes/separated/separated.css Request Transfer Size: 1605 Critical Request Chains Child: request startTime: 50013.8649 Request Response Received Time: 50014.140307 Request End Time: 50014.140312 Request URL: https://www.liquidpurple.com/media/foundry/css/foundry.min.css?7cac7401e143c0858e706f5349fab9a5=1 Request Transfer Size: 20094 Critical Request Chains Child: request startTime: 50013.870574 Request Response Received Time: 50013.947334 Request End Time: 50013.94734 Request URL: https://www.liquidpurple.com/media/system/js/mootools-core.js?3efd14aada41c7ec345fd8f917dd4257 Request Transfer Size: 27784 Critical Request Chains Child: request startTime: 50013.860805 Request Response Received Time: 50014.008473 Request End Time: 50014.008476 Request URL: https://www.liquidpurple.com/components/com_seofront/assets/css/all.css Request Transfer Size: 13187 Critical Request Chains Child: request startTime: 50013.870281 Request Response Received Time: 50014.023955 Request End Time: 50014.023959 Request URL: https://www.liquidpurple.com/templates/purity_iii/js/script.js Request Transfer Size: 1564 Critical Request Chains Child: request startTime: 50013.862705 Request Response Received Time: 50014.025473 Request End Time: 50014.025475 Request URL: https://www.liquidpurple.com/templates/purity_iii/css/off-canvas.css Request Transfer Size: 2435 Critical Request Chains Child: request startTime: 50013.869087 Request Response Received Time: 50013.971887 Request End Time: 50013.97189 Request URL: https://www.liquidpurple.com/media/jui/js/jquery-migrate.min.js?3efd14aada41c7ec345fd8f917dd4257 Request Transfer Size: 4436 Critical Request Chains Child: request startTime: 50013.862937 Request Response Received Time: 50013.898062 Request End Time: 50013.898066 Request URL: https://www.liquidpurple.com/templates/purity_iii/css/custom.css Request Transfer Size: 6731 Critical Request Chains Child: request startTime: 50013.87308 Request Response Received Time: 50013.952178 Request End Time: 50013.952181 Request URL: https://www.liquidpurple.com/media/com_joomtestimonials/js/swiper.min.js Request Transfer Size: 32457 Critical Request Chains Child: request startTime: 50013.869388 Request Response Received Time: 50013.940752 Request End Time: 50013.940757 Request URL: https://www.liquidpurple.com/plugins/system/t3/base-bs3/js/jquery.tap.min.js Request Transfer Size: 1264 Critical Request Chains Child: request startTime: 50013.866474 Request Response Received Time: 50014.026438 Request End Time: 50014.026442 Request URL: https://www.liquidpurple.com/components/com_seofront/assets/bootstrap/js/bootstrap.min.js Request Transfer Size: 10359 Critical Request Chains Child: request startTime: 50013.864569 Request Response Received Time: 50014.066204 Request End Time: 50014.066207 Request URL: https://www.liquidpurple.com/media/com_joomtestimonials/css/animate.css Request Transfer Size: 5154 Critical Request Chains Child: request startTime: 50013.869173 Request Response Received Time: 50014.065556 Request End Time: 50014.065563 Request URL: https://www.liquidpurple.com/plugins/system/t3/base-bs3/bootstrap/js/bootstrap.js?3efd14aada41c7ec345fd8f917dd4257 Request Transfer Size: 16955 Critical Request Chains Child: request startTime: 50013.874559 Request Response Received Time: 50013.997398 Request End Time: 50013.997401 Request URL: https://www.liquidpurple.com/media/com_payplans/scripts/site-5.0.3.min.js Request Transfer Size: 81042 Critical Request Chains Child: request startTime: 50013.869789 Request Response Received Time: 50013.98369 Request End Time: 50013.983697 Request URL: https://www.liquidpurple.com/plugins/system/t3/base-bs3/js/off-canvas.js Request Transfer Size: 2832 Critical Request Chains Child: request startTime: 50013.86123 Request Response Received Time: 50013.972353 Request End Time: 50013.972356 Request URL: https://www.liquidpurple.com/components/com_seofront/assets/css/style.css Request Transfer Size: 9086 Critical Request Chains Child: request startTime: 50013.862847 Request Response Received Time: 50013.898623 Request End Time: 50013.898626 Request URL: https://www.liquidpurple.com/templates/purity_iii/fonts/font-awesome/css/font-awesome.min.css Request Transfer Size: 7429 Critical Request Chains Child: request startTime: 50013.87184 Request Response Received Time: 50014.025072 Request End Time: 50014.025075 Request URL: https://www.liquidpurple.com/components/com_roksprocket/assets/js/roksprocket.js Request Transfer Size: 1051 Critical Request Chains Child: request startTime: 50013.863529 Request Response Received Time: 50014.008863 Request End Time: 50014.008866 Request URL: https://www.liquidpurple.com/media/com_joomtestimonials/css/style.css Request Transfer Size: 3083 Critical Request Chains Child: request startTime: 50013.865022 Request Response Received Time: 50014.007503 Request End Time: 50014.007506 Request URL: https://www.liquidpurple.com/media/foundry/css/vendor/fontawesome/css/all.min.css?7cac7401e143c0858e706f5349fab9a5=1 Request Transfer Size: 13335 Critical Request Chains Child: request startTime: 50013.871184 Request Response Received Time: 50013.906177 Request End Time: 50013.906181 Request URL: https://www.liquidpurple.com/components/com_roksprocket/assets/js/mootools-mobile.js Request Transfer Size: 2690 Critical Request Chains Child: request startTime: 50013.870723 Request Response Received Time: 50013.990685 Request End Time: 50013.99069 Request URL: https://www.liquidpurple.com/media/system/js/core.js?3efd14aada41c7ec345fd8f917dd4257 Request Transfer Size: 3787 Critical Request Chains Child: request startTime: 50013.873596 Request Response Received Time: 50014.011145 Request End Time: 50014.011148 Request URL: https://www.liquidpurple.com/media/foundry/scripts/core.min.js?7cac7401e143c0858e706f5349fab9a5=1 Request Transfer Size: 11000 Critical Request Chains Child: request startTime: 50013.869963 Request Response Received Time: 50013.991677 Request End Time: 50013.99168 Request URL: https://www.liquidpurple.com/plugins/system/t3/base-bs3/js/script.js Request Transfer Size: 2694 Critical Request Chains Child: request startTime: 50013.87261 Request Response Received Time: 50013.947941 Request End Time: 50013.947944 Request URL: https://www.liquidpurple.com/components/com_roksprocket/layouts/strips/assets/js/strips.js Request Transfer Size: 3774 Critical Request Chains Child: request startTime: 50013.861643 Request Response Received Time: 50014.006551 Request End Time: 50014.006554 Request URL: https://www.liquidpurple.com/templates/purity_iii/css/template.css Request Transfer Size: 14580 Critical Request Chains Child: request startTime: 50013.872287 Request Response Received Time: 50013.971572 Request End Time: 50013.971576 Request URL: https://www.liquidpurple.com/components/com_roksprocket/assets/js/roksprocket.request.js Request Transfer Size: 2023 Critical Request Chains Child: request startTime: 50013.860957 Request Response Received Time: 50014.007002 Request End Time: 50014.007005 Request URL: https://www.liquidpurple.com/components/com_seofront/assets/css/stylesheet.css Request Transfer Size: 12751 Critical Request Chains Child: request startTime: 50013.86594 Request Response Received Time: 50014.028229 Request End Time: 50014.028232 Request URL: https://www.liquidpurple.com/media/foundry/css/utilities.min.css?7cac7401e143c0858e706f5349fab9a5=1 Request Transfer Size: 7161 Critical Request Chains Child: request startTime: 50013.872979 Request Response Received Time: 50013.991387 Request End Time: 50013.99139 Request URL: https://www.liquidpurple.com/components/com_roksprocket/layouts/strips/assets/js/strips-speeds.js Request Transfer Size: 792 Critical Request Chains Child: request startTime: 50013.86883 Request Response Received Time: 50014.009387 Request End Time: 50014.00939 Request URL: https://www.liquidpurple.com/media/jui/js/jquery-noconflict.js?3efd14aada41c7ec345fd8f917dd4257 Request Transfer Size: 379 Critical Request Chains Child: request startTime: 50013.86369 Request Response Received Time: 50013.914914 Request End Time: 50013.914923 Request URL: https://use.fontawesome.com/releases/v5.8.2/css/all.css Request Transfer Size: 12915
Audits - Final Screenshot
ID:
final-screenshot
Title:
Final Screenshot
Description:
The last screenshot captured of the pageload.
Score:
Unknown
Score Display Mode:
informative
Type:
screenshot
Timing:
3037
Timestamp:
50014732664
Data:
Audits - Offscreen Images
ID:
offscreen-images
Title:
Defer offscreen images
Description:
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn more](https://web.dev/offscreen-images/).
Score:
1
Score Display Mode:
numeric
Numeric Value:
0
Overall Savings (ms):
0
Overall Savings Bytes:
0
Type:
opportunity
Audits - Largest Contentful Paint
ID:
largest-contentful-paint
Title:
Largest Contentful Paint
Description:
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn more](https://web.dev/lighthouse-largest-contentful-paint/)
Score:
0.73
Score Display Mode:
numeric
Display Value:
1.7 s
Numeric Value:
1710
Diagnostics Items: Total Byte Weight: 1705492 Max RTT: 0.00065749215421274 Throughput: 30660527477.103 Num Tasks Over 10ms: 15 Num Tasks Over 500ms: 0 Total Task Time: 859.595 Num Tasks: 723 Num Tasks Over 100ms: 2 Num Tasks Over 50ms: 4 RTT: 0.00065749215421274 Num Tasks Over 25ms: 7 Num Stylesheets: 24 Num Scripts: 42 Main Document Transfer Size: 131191 Num Requests: 103 Num Fonts: 7
ID:
resource-summary
Title:
Keep request counts low and transfer sizes small
Description:
To set budgets for the quantity and size of page resources, add a budget.json file. [Learn more](https://web.dev/use-lighthouse-for-performance-budgets/).
Score:
Unknown
Score Display Mode:
informative
Display Value:
98 requests • 1,666 KiB
Type:
table
Resource Summary Items: Resource Type: total Label: Total Request Count: 98 Transfer Size: 1705492 Resource Summary Items: Resource Type: image Label: Image Request Count: 20 Transfer Size: 494809 Resource Summary Items: Resource Type: script Label: Script Request Count: 42 Transfer Size: 475489 Resource Summary Items: Resource Type: font Label: Font Request Count: 7 Transfer Size: 404444 Resource Summary Items: Resource Type: stylesheet Label: Stylesheet Request Count: 24 Transfer Size: 198003 Resource Summary Items: Resource Type: document Label: Document Request Count: 1 Transfer Size: 131191 Resource Summary Items: Resource Type: other Label: Other Request Count: 4 Transfer Size: 1556 Resource Summary Items: Resource Type: media Label: Media Request Count: 0 Transfer Size: 0 Resource Summary Items: Resource Type: third-party Label: Third-party Request Count: 7 Transfer Size: 81636
Audits - Server Response Time
ID:
server-response-time
Title:
Reduce initial server response time
Description:
Keep the server response time for the main document short because all other requests depend on it. [Learn more](https://web.dev/time-to-first-byte/).
Score:
0
Score Display Mode:
binary
Display Value:
Root document took 2,150 ms
Numeric Value:
2154.319
Type:
opportunity
Overall Savings (ms):
2054.319
Audits - Font Display
ID:
font-display
Title:
Ensure text remains visible during webfont load
Description:
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. [Learn more](https://web.dev/font-display/).
Score:
0
Score Display Mode:
binary
Type:
table
Headings (print_r):
ID:
efficient-animated-content
Title:
Use video formats for animated content
Description:
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. [Learn more](https://web.dev/efficient-animated-content/)
Score:
1
Score Display Mode:
numeric
Numeric Value:
0
Type:
opportunity
Overall Savings Bytes:
0
Overall Savings (ms):
0
Headings (print_r):
Array
(
)
Items (print_r):
Array
(
)
Audits - Metrics
ID:
metrics
Title:
Metrics
Description:
Collects all available metrics.
Score:
Unknown
Score Display Mode:
informative
Numeric Value:
1687
Type:
debugdata
Speed Index:
2270
Observed First Meaningful Paint (ts):
50014444953
First Meaningful Paint:
1450
Observed First Contentful Paint:
2620
Observed Navigation Start (ts):
50011696085
Cumulative Layout Shift:
0.0068119595846832
Observed Largest Contentful Paint:
2749
Observed Trace End (ts):
50018115603
Observed Dom Content Loaded:
3021
Observed Cumulative Layout Shift:
0.0068119595846832
Observed Dom Content Loaded (ts):
50014717079
Largest Contentful Paint:
1710
Observed First Visual Change (ts):
50014315085
Observed Speed Index:
2756
Observed Last Visual Change (ts):
50014732085
Observed Largest Contentful Paint (ts):
50014444953
Max Potential FID:
130
Observed Navigation Start:
0
Observed Last Visual Change:
3036
Observed First Paint:
2620
Estimated Input Latency:
Unknown
Observed Load (ts):
50014886770
First Contentful Paint:
1160
Observed Speed Index (ts):
50014452509
Observed First Meaningful Paint:
2749
Total Blocking Time:
61
Observed Load:
3191
Observed First Contentful Paint (ts):
50014315712
First CPU Idle:
Unknown
Observed First Paint (ts):
50014315712
Observed Trace End:
6420
Interactive:
1687
Observed First Visual Change:
2619
LCP Invalidated:
Audits - Total Blocking Time
ID:
total-blocking-time
Title:
Total Blocking Time
Description:
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. [Learn more](https://web.dev/lighthouse-total-blocking-time/).
Score:
1
Score Display Mode:
numeric
Display Value:
60 ms
Numeric Value:
61
Audits - Uses Text Compression
ID:
uses-text-compression
Title:
Enable text compression
Description:
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more](https://web.dev/uses-text-compression/).
Score:
1
Score Display Mode:
numeric
Numeric Value:
0
Overall Savings (ms):
0
Type:
opportunity
Overall Savings Bytes:
0
Headings (print_r):
Array
(
)
Items (print_r):
Array
(
)
Audits - Total Byte Weight
ID:
total-byte-weight
Title:
Avoids enormous network payloads
Description:
Large network payloads cost users real money and are highly correlated with long load times. [Learn more](https://web.dev/total-byte-weight/).
Score:
1
Score Display Mode:
numeric
Display Value:
Total size was 1,666 KiB
Numeric Value:
1705492
Type:
table
Audits - Total Byte Weight - Items
Total Byte Weight - Items: Total Bytes: 131191 URL: https://www.liquidpurple.com/ Total Byte Weight - Items: Total Bytes: 81042 URL: https://www.liquidpurple.com/media/com_payplans/scripts/site-5.0.3.min.js Total Byte Weight - Items: Total Bytes: 78547 URL: https://www.liquidpurple.com/media/foundry/css/vendor/fontawesome/webfonts/fa-solid-900.woff2 Total Byte Weight - Items: Total Bytes: 77511 URL: https://www.liquidpurple.com/templates/purity_iii/fonts/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0 Total Byte Weight - Items: Total Bytes: 71678 URL: https://www.liquidpurple.com/media/font-roboto/Roboto-Light.woff Total Byte Weight - Items: Total Bytes: 71626 URL: https://www.liquidpurple.com/media/font-roboto/RobotoCondensed-Bold.woff Total Byte Weight - Items: Total Bytes: 70210 URL: https://www.liquidpurple.com/media/font-roboto/RobotoCondensed-Light.woff Total Byte Weight - Items: Total Bytes: 68229 URL: https://www.liquidpurple.com/images/portfolio/2021_Mobile_Bicycles_Repair-sm.jpg Total Byte Weight - Items: Total Bytes: 60801 URL: https://www.liquidpurple.com/images/portfolio/2021_Affordable_Therapist-sm.jpg Total Byte Weight - Items: Total Bytes: 55374 URL: https://www.liquidpurple.com/images/portfolio/2021_LADF_New_Markets-sm.jpg
Audits - Unused Javascript
ID:
unused-javascript
Title:
Reduce unused JavaScript
Description:
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn more](https://web.dev/unused-javascript/).
Score:
0.93
Score Display Mode:
numeric
Display Value:
Potential savings of 74 KiB
Numeric Value:
80
Type:
opportunity
Overall Savings (ms):
80
Overall Savings Bytes:
76198
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Score: 1 Potential savings of 18 KiB
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading.Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Score: 1
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Score: 0.93 Potential savings of 74 KiB
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Score: 1
Type
Time Spent
1
Script Evaluation
326.02 MS
2
Style & Layout
256.00 MS
3
Other
140.01 MS
4
Parse HTML & CSS
81.50 MS
5
Script Parsing & Compilation
27.88 MS
6
Rendering
21.73 MS
7
Garbage Collection
6.46 MS
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Score: 1 No improvement needed.
Resource Summary
Keep request counts low and transfer sizes small. To set budgets for the quantity and size of page resources, add a budget.json file. 98 requests • 1,666 KiB
Resource Type
Requests
Transfer Size
1
Image
20
483.21 KB
2
Script
42
464.34 KB
3
Font
7
394.96 KB
4
Stylesheet
24
193.36 KB
5
Document
1
128.12 KB
6
Other
4
1.52 KB
7
Media
0
0.00 KB
8
Third-party
7
79.72 KB
98
1,666.00 KB
Minify CSS
Minifying CSS files can reduce network payload sizes. Score: 0.93 Potential savings of 17 KiB
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Score: 0.5 Potential savings of 770 ms
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Score: 0.83 Potential savings of 318 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Score: 1 No improvement needed.
Avoid chaining critical requests
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Score: 59 chains found