Spain · Madrid Completed: Apr 22, 2026 20:54 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 72 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Several missing protections leave your users and data exposed.
Major barriers for users with disabilities — up to 15% of your audience.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Strong compliance posture across regulations.
Rich content metadata — your pages look great everywhere.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
1 link(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
5 image(s) missing alt attribute
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/e1846101-b5fd-48b4-b2a3-737a14543a13)<a href="https://beavercheck.com/results/e1846101-b5fd-48b4-b2a3-737a14543a13"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fextendthemes.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fextendthemes.comThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
6 barrier(s) likely increasing bounce by ~22%.
Page loads in 2.5s
+5% bounceEvery additional 100ms above 2.5s costs conversions — you're 1ms over
Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image
High main-thread blocking time
+2% bouncePage is non-interactive for 556ms after first paint
Fix: Defer third-party scripts and split large bundles
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Layout shifts during page load
+3% bounceContent movement causes mis-clicks on CTAs and form fields
Fix: Add width/height to images; reserve space for late-loading embeds
5 broken link(s) on the page
+5% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$450 investment → $3.10/month returns + USD 150,000 risk avoided
$450
4h · 5 findings
$3.10 /mo
~$37 / year
USD 150,000
if kept compliant
$150 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
4.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$12,501 / month at risk
~$150,010 / year if left unfixed
$150,000
+4 more
$0.84 /mo
10558.8 MB/mo × 0.080 USD/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.42 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.50 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
556 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.136
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.44 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
12.85 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| /wp-content/themes/mesmerize-pro/assets/fonts/fontawesome... | 195 ms |
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| extendstudio.postaffiliatepro.com/scripts/63joaw | 5.4 KiB | 828 ms |
| sbl.onfastspring.com/sbl/0.9.4/fastspring-builder.min.js | 11.6 KiB | 967 ms |
| extendthemes.com/wp-includes/js/jquery/jquery.min.js | 31.7 KiB | 668 ms |
| extendthemes.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js | 1003 B |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded | extendthemes.com/wp-content/uploads/2017/11/themes-screens-opex-1.jpg | 70.2 KiB | 14.0 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| extendthemes.com/ | 1.1 s |
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
We create WP themes that take the Customizer to the next level
Check out our th… div#page > div.header-wrapper > div.header-homepage > div.header-description | 0.077 |
We create WP themes that take the Customizer to the next level
Check out our th… div#page > div.header-wrapper > div.header-homepage > div.header-description | 0.039 |
div.navigation-bar > div.navigation-wrapper > div.row > div.main_menu_col div.navigation-bar > div.navigation-wrapper > div.row > div.main_menu_col | 0.017 |
We create WP themes that take the Customizer to the next level div.header-description-top > div.header-content > div.align-holder > h1.hero-title | 0.002 |
Check out our themes div.header-content > div.align-holder > div.header-buttons-wrapper > a.button | 0.000 |
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| extendthemes.com/ | 1.1 s | 37 ms | 17 ms |
| www.googletagmanager.com/gtm.js?id=GTM-K727XDQ | 311 ms | 261 ms | 47 ms |
| /main/wp-content/cache/autoptimize/js/autoptimize_27c2b04... | 305 ms | 210 ms | 35 ms |
| www.googletagmanager.com/gtag/js?id=G-KXM44XGGS1&cx=c>m=4e64k0 | 300 ms | 242 ms | 57 ms |
| Unattributable | 257 ms | 6.7 ms | 0.0 ms |
| www.google-analytics.com/analytics.js | 186 ms | 138 ms | 18 ms |
| www.googletagmanager.com/gtag/js?id=UA-109464846-1 | 184 ms | 150 ms | 31 ms |
| extendthemes.com/wp-includes/js/jquery/jquery.min.js | 173 ms | 103 ms | 9.2 ms |
| /main/wp-content/plugins/autoptimize/classes/external/js/... | 147 ms | 47 ms | 1.1 ms |
| beacon-v2.helpscout.net/static/js/main.c8916e6f.js | 119 ms | 100 ms | 11 ms |
| www.googletagmanager.com/gtag/js?id=G-KXM44XGGS1 | 79 ms | 24 ms | 54 ms |
| www.googletagmanager.com/gtag/js?id=GT-5RFL56D&cx=c>m=4e64k0 | 71 ms | 27 ms | 43 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.4 s |
| Style & Layout | 710 ms |
| Other | 608 ms |
| Script Parsing & Compilation | 340 ms |
| Rendering | 240 ms |
| Parse HTML & CSS | 115 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| @charset "UTF-8";#start-resizable-editor-section{display:none} … | 57.6 KiB | 54.6 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=GT-5RFL56D&cx=c>m=4e64k0 | 162.9 KiB | 108.7 KiB |
| www.googletagmanager.com/gtag/js?id=G-KXM44XGGS1 | 162.9 KiB | 108.7 KiB |
| /main/wp-content/cache/autoptimize/js/autoptimize_27c2b04... | 103.5 KiB | 67.3 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-K727XDQ | 155.1 KiB | 66.3 KiB |
| www.googletagmanager.com/gtag/js?id=G-KXM44XGGS1&cx=c>m=4e64k0 | 162.9 KiB | 66.3 KiB |
| www.googletagmanager.com/gtag/js?id=UA-109464846-1 | 124.9 KiB | 62.8 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded | extendthemes.com/wp-content/uploads/2017/11/themes-screens-opex-1.jpg |
ExtendThemes div.row > div.logo_col > a.custom-logo-link > img.custom-logo | extendthemes.com/wp-content/uploads/2017/11/logo-extendthemes-1.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Check out our themes div.header-content > div.align-holder > div.header-buttons-wrapper > a.button |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
CONTACT US div.gridContainer > div.row > div.col-xs-12 > a.button |
GET ONE PAGE EXPRESS div.gridContainer > div.row > div > a.button |
GET MESMERIZE div.gridContainer > div.row > div > a.button |
GET MATERIALIS div.gridContainer > div.row > div > a.button |
GET EMPOWERWP div.gridContainer > div.row > div > a.button |
GET HIGHLIGHT div.gridContainer > div.row > div > a.button |
© 2026 ExtendThemes. div.row > div.col-xs-12 > div.muted > p.copyright |
Home div.horizontal_footer_menu > ul#footer_menu > li#menu-item-416 > a |
Themes div.horizontal_footer_menu > ul#footer_menu > li#menu-item-417 > a |
Support div.horizontal_footer_menu > ul#footer_menu > li#menu-item-419 > a |
Blog div.horizontal_footer_menu > ul#footer_menu > li#menu-item-491 > a |
License div.horizontal_footer_menu > ul#footer_menu > li#menu-item-415 > a |
Terms div.horizontal_footer_menu > ul#footer_menu > li#menu-item-783 > a |
Privacy Policy div.horizontal_footer_menu > ul#footer_menu > li#menu-item-790 > a |
Members Area div.horizontal_footer_menu > ul#footer_menu > li#menu-item-13864 > a |
I ACCEPT body.home > div#eu-cookie-bar > button#euCookieAcceptWP |
These are opportunities to improve the legibility of your content.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
One Page Drag & Drop Theme div.col-xs-12 > div.card > div.space-bottom > h4 |
@SwirishNinja div.row > div.col-xs-12 > div.card > h6 |
14 DAYS MONEY BACK GUARANTEE div.col-xs-12 > div.row > div.col-xs-12 > h5 |
ExtendThemes div.row > div.col-xs-12 > div.footer-logo > h4 |
These are opportunities to improve keyboard navigation in your application.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
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 how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.navigation-wrapper > div.row > div.main_menu_col > a div.navigation-wrapper > div.row > div.main_menu_col > a |
div#page > div#page-content > div.content > a div#page > div#page-content > div.content > a |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.touch-enabled html.touch-enabled |
These items highlight common accessibility best practices.
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Access to XMLHttpRequest at 'https://app.colibriwp.com/current-user' from origin 'https://extendthemes.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. | |
Failed to load resource: net::ERR_FAILED |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
673 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
746 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
14 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.077
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.43 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
2.70 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| /wp-content/themes/mesmerize-pro/assets/fonts/fontawesome... | 40 ms |
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| extendstudio.postaffiliatepro.com/scripts/63joaw | 5.4 KiB | 275 ms |
| sbl.onfastspring.com/sbl/0.9.4/fastspring-builder.min.js | 11.6 KiB | 250 ms |
| extendthemes.com/wp-includes/js/jquery/jquery.min.js | 31.7 KiB | 54 ms |
| extendthemes.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js | 1007 B |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded | extendthemes.com/wp-content/uploads/2017/11/themes-screens-opex-1.jpg | 70.2 KiB | 47.6 KiB |
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded | extendthemes.com/wp-content/uploads/2017/11/themes-screens-mesmerize-1.jpg | 65.2 KiB | 42.6 KiB |
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded | /wp-content/uploads/2018/06/cropped-themes-screens-materi... | 57.2 KiB | 34.6 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| @charset "UTF-8";#start-resizable-editor-section{display:none} … | 57.5 KiB | 53.4 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-KXM44XGGS1&cx=c>m=4e64k0 | 163.0 KiB | 108.8 KiB |
| www.googletagmanager.com/gtag/js?id=G-KXM44XGGS1 | 162.9 KiB | 108.7 KiB |
| /main/wp-content/cache/autoptimize/js/autoptimize_54195cc... | 111.2 KiB | 73.9 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-K727XDQ | 155.1 KiB | 66.3 KiB |
| www.googletagmanager.com/gtag/js?id=GT-5RFL56D&cx=c>m=4e64k0 | 163.0 KiB | 66.1 KiB |
| www.googletagmanager.com/gtag/js?id=UA-109464846-1 | 124.9 KiB | 62.8 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded | extendthemes.com/wp-content/uploads/2017/11/themes-screens-opex-1.jpg |
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded | extendthemes.com/wp-content/uploads/2017/11/themes-screens-mesmerize-1.jpg |
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded | /wp-content/uploads/2018/06/cropped-themes-screens-materi... |
ExtendThemes div.row > div.logo_col > a.custom-logo-link > img.custom-logo | extendthemes.com/wp-content/uploads/2017/11/logo-extendthemes-1.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
VIEW THEMES div.row > div.custom_area_col > div.navigation-custom-area > a.button |
Check out our themes div.header-content > div.align-holder > div.header-buttons-wrapper > a.button |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
See on WordPress.org div.row > div.col-xs-12 > div.card > a |
CONTACT US div.gridContainer > div.row > div.col-xs-12 > a.button |
GET ONE PAGE EXPRESS div.gridContainer > div.row > div > a.button |
GET MESMERIZE div.gridContainer > div.row > div > a.button |
GET MATERIALIS div.gridContainer > div.row > div > a.button |
GET EMPOWERWP div.gridContainer > div.row > div > a.button |
GET HIGHLIGHT div.gridContainer > div.row > div > a.button |
© 2026 ExtendThemes. div.row > div.col-xs-12 > div.muted > p.copyright |
Home div.horizontal_footer_menu > ul#footer_menu > li#menu-item-416 > a |
Themes div.horizontal_footer_menu > ul#footer_menu > li#menu-item-417 > a |
Support div.horizontal_footer_menu > ul#footer_menu > li#menu-item-419 > a |
Blog div.horizontal_footer_menu > ul#footer_menu > li#menu-item-491 > a |
License div.horizontal_footer_menu > ul#footer_menu > li#menu-item-415 > a |
Terms div.horizontal_footer_menu > ul#footer_menu > li#menu-item-783 > a |
Privacy Policy div.horizontal_footer_menu > ul#footer_menu > li#menu-item-790 > a |
Members Area div.horizontal_footer_menu > ul#footer_menu > li#menu-item-13864 > a |
I ACCEPT body.home > div#eu-cookie-bar > button#euCookieAcceptWP |
These are opportunities to improve the legibility of your content.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
One Page Drag & Drop Theme div.col-xs-12 > div.card > div.space-bottom > h4 |
@SwirishNinja div.row > div.col-xs-12 > div.card > h6 |
14 DAYS MONEY BACK GUARANTEE div.col-xs-12 > div.row > div.col-xs-12 > h5 |
ExtendThemes div.row > div.col-xs-12 > div.footer-logo > h4 |
These are opportunities to improve keyboard navigation in your application.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded |
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded |
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
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 how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#page > div#page-content > div.content > a div#page > div#page-content > div.content > a |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.has-offscreen html.has-offscreen |
These items highlight common accessibility best practices.
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Access to XMLHttpRequest at 'https://app.colibriwp.com/current-user' from origin 'https://extendthemes.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. | |
Failed to load resource: net::ERR_FAILED |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded |
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded |
div.card > div.contentswap-effect > div.initial-image > img.lazyloaded div.card > div.contentswap-effect > div.initial-image > img.lazyloaded |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
div.card > div.contentswap-effect > div.initial-image > img.lazyload div.card > div.contentswap-effect > div.initial-image > img.lazyload |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback