C — https://gtmetrix.com | BeaverCheck Audit

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Missing signals may be hurting your search visibility.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

AngularJS · 251 peers

You 73

Avg 73

At average

0 50 100

Better than 46% of AngularJS sites See full AngularJS benchmark →

Cloudflare Turnstile · 265 peers

You 73

Avg 73

At average

0 50 100

Better than 44% of Cloudflare Turnstile sites See full Cloudflare Turnstile benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

20 third-party resources (51% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

Cross-Origin-Embedder-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

Cross-Origin-Opener-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fgtmetrix.com)](https://beavercheck.com/results/114772a8-3c6b-48c0-954d-16173f738727)

HTML

<a href="https://beavercheck.com/results/114772a8-3c6b-48c0-954d-16173f738727"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgtmetrix.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fgtmetrix.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 9.6s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

4 security gaps detected — browsers may warn visitors about your site.

Your LCP is 9.6s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~29%.

Speed (2)

Page takes 9.6s to load

+12% bounce

Users abandon at ~3s — you're 7.1s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 1.1s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$400 investment → $4,484/month returns + USD 150,000 risk avoided

Payback period: < 1 month First-year ROI: +13351%

Investment

$400

4h · 5 findings

Monthly returns

$4,484 /mo

~$53,802 / year

Conversions recovered $4,483
Bandwidth savings $0.33

Regulatory risk avoided

USD 150,000

if kept compliant

ADA Title III USD 150,000

Payback period

0 12mo 24mo

$200 — 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.

Full methodology & sources

Estimated Remediation Cost

$400

4.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$200 4 fixes in ~120 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$12,500 / month at risk

~$150,004 / year if left unfixed

Compliance Risk

$150,000

ADA Title III

No <nav> landmark found
ADA Title III: USD 25,000 – USD 150,000
Skip navigation link is missing (WCAG 2.4.1)
ADA Title III: USD 25,000 – USD 150,000

Bandwidth Waste

$0.33 /mo

4126.9 MB/mo × 0.080 USD/GB

Optimize transfer: save ~413 KB per page load
Saves $0.33/mo

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.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 2 critical issues to capture this value

How this is calculated

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

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

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.

1.53 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

9.63 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

1.07 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.009

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.36 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.

9.69 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

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

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
app.termly.io/resource-blocker/fbd418dc-a86f-4230-b813-4dc2d2aa8556	14400.0 s	143.6 KiB
gtmetrix.com/static/r322/js/gtmetrix.min.js	14400.0 s	122.6 KiB
gtmetrix.com/static/r322/images/home/features-history.png	14400.0 s	88.9 KiB
gtmetrix.com/static/r322/css/gtmetrix.min.css	14400.0 s	59.3 KiB
cdn.mxpnl.com/libs/mixpanel-2-latest.min.js	600.0 s	31.5 KiB
gtmetrix.com/static/r322/images/home/features-crux.webp	14400.0 s	33.3 KiB
gtmetrix.com/static/r322/fonts/MavenPro-medium-500.woff2	14400.0 s	23.7 KiB
gtmetrix.com/static/r322/images/home/features-alerts.webp	14400.0 s	22.3 KiB
app.termly.io/resource-blocker/support/894-6156b36a131577c56e7e.min.js	14400.0 s	8.4 KiB
gtmetrix.com/static/r322/images/bg-body.png	14400.0 s	5.0 KiB
gtmetrix.com/static/r322/images/home/logo-godaddy.png	14400.0 s	3.9 KiB
app.termly.io/resource-blocker/support/808-26e9c6c7a3bd048ed656.min.js	14400.0 s	3.2 KiB
gtmetrix.com/static/r322/images/home/logo-adobe.png	14400.0 s	2.7 KiB
app.termly.io/resource-blocker/support/524-7d36cb122791702e3df2.min.js	14400.0 s	2.7 KiB
cdn.mxpnl.com/libs/mixpanel-js-wrapper.min.js	600.0 s	1.7 KiB
app.termly.io/resource-blocker/support/377-e518d8a5c599aa1c5977.min.js	14400.0 s	873 B

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV

nodeLabel: Test your website speed GTmetrix tells you how your website performs, why it's …

path: 1,HTML,1,BODY,1,DIV,2,MAIN,0,ARTICLE,0,SECTION,0,DIV

selector: main.page-home-content > article > section.home-section-analyze > div.home-section-analyze-container

snippet: <div class="home-section-analyze-container theme-modal-btns">

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
gtmetrix.com/static/r322/css/gtmetrix.min.css	59.3 KiB	450 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Report History graph `article > section.layout-zebra-section > div.layout-zebra-section-content > img.home-img-shadow`	gtmetrix.com/static/r322/images/home/features-history.png	88.7 KiB	57.3 KiB
CrUX Report `section.layout-zebra-section > div.layout-zebra-section-content > picture > img`	gtmetrix.com/static/r322/images/home/features-crux.webp	33.2 KiB	13.2 KiB
GTmetrix vs Lighthouse (DevTools) `div.home-section-news-container > div.card > a.home-section-news-item-img > img`	/blog/wp-content/uploads/2025/12/GTmetrix-vs-DevTools-fea...	26.7 KiB	8.6 KiB
GTmetrix Alternatives `div.home-section-news-container > div.card > a.home-section-news-item-img > img`	/blog/wp-content/uploads/2025/11/GTmetrix-Alternatives-fe...	25.8 KiB	7.7 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

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

Estimated savings: 1.6 s 344.2 KiB

URL	Transfer Size	Est Savings
gtmetrix.com/static/r322/js/gtmetrix.min.js	122.5 KiB	95.6 KiB
sst.gtmetrix.com/gtag/js?id=G-GSJLD4V4YY&cx=c&gtm=4e64h1	170.3 KiB	66.8 KiB
www.googletagmanager.com/gtag/js?id=AW-17360026842&cx=c&gtm=4e64h1	143.5 KiB	65.7 KiB
sst.gtmetrix.com/tm?origin=https://gtmetrix.com	156.8 KiB	61.6 KiB
app.termly.io/resource-blocker/fbd418dc-a86f-4230-b813-4dc2d2aa8556	143.3 KiB	54.5 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
gtmetrix.com/	578 ms	24 ms	4.3 ms
Unattributable	432 ms	11 ms	0.0 ms
app.termly.io/resource-blocker/fbd418dc-a86f-4230-b813-4dc2d2aa8556	415 ms	341 ms	48 ms
sst.gtmetrix.com/tm?origin=https://gtmetrix.com	400 ms	329 ms	49 ms
sst.gtmetrix.com/gtag/js?id=G-GSJLD4V4YY&cx=c&gtm=4e64h1	344 ms	274 ms	52 ms
gtmetrix.com/static/r322/js/gtmetrix.min.js	280 ms	191 ms	40 ms
www.googletagmanager.com/gtag/js?id=AW-17360026842&cx=c&gtm=4e64h1	243 ms	202 ms	40 ms
cdn.mxpnl.com/libs/mixpanel-2-latest.min.js	85 ms	74 ms	9.9 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.5 s
Other	581 ms
Style & Layout	414 ms
Script Parsing & Compilation	248 ms
Parse HTML & CSS	61 ms
Rendering	52 ms
Garbage Collection	18 ms

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,343 KiB

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 11 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 170 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

Accessibility

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We're relied on by the best, with 1,393,490,164 pages analyzed so far. `article > section.home-section-analyzed > div.home-section-analyzed-content > h2.home-section-analyzed-title`
Try GTmetrix FREE today `article > section.home-section > div.features-section-start-btns > a.btn`
Get full access with PRO `article > section.home-section > div.features-section-start-btns > a.btn`
Read more `div.card > div.home-section-news-item-content > p.home-section-news-btn > a.btn`
Read more `div.card > div.home-section-news-item-content > p.home-section-news-btn > a.btn`
Read the Blog `article > section.home-section-news > div.home-section-news-link > a.btn`
Additional Test Locations only available with GTmetrix PRO. `div.layout-zebra-section-content > div.home-content-text > p > a`

These are opportunities to improve the legibility of your content.

Navigation

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Product `div.footer-content > div.footer-links > div.footer-links-column > h6`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.page-home > div.page-wrapper > header.header > a.site-nav-home `body.page-home > div.page-wrapper > header.header > a.site-nav-home`
nav > div.user-nav > div.user-nav-responsive > a.site-nav-menu `nav > div.user-nav > div.user-nav-responsive > a.site-nav-menu`
footer.footer > div.footer-content-wrapper > div.footer-about > a.site-nav-home `footer.footer > div.footer-content-wrapper > div.footer-about > a.site-nav-home`
body.page-home > div#menu-site-nav > a.menu-close `body.page-home > div#menu-site-nav > a.menu-close`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

100

Best Practices

General

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 about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
sst.gtmetrix.com/gtag/js?id=G-GSJLD4V4YY&cx=c&gtm=4e64h1
app.termly.io/resource-blocker/support/894-6156b36a131577c56e7e.min.js	app.termly.io/resource-blocker/support/894-6156b36a131577c56e7e.min.js.map
app.termly.io/resource-blocker/support/808-26e9c6c7a3bd048ed656.min.js	app.termly.io/resource-blocker/support/808-26e9c6c7a3bd048ed656.min.js.map
app.termly.io/resource-blocker/support/524-7d36cb122791702e3df2.min.js	app.termly.io/resource-blocker/support/524-7d36cb122791702e3df2.min.js.map
app.termly.io/resource-blocker/support/377-e518d8a5c599aa1c5977.min.js	app.termly.io/resource-blocker/support/377-e518d8a5c599aa1c5977.min.js.map
app.termly.io/resource-blocker/fbd418dc-a86f-4230-b813-4dc2d2aa8556	app.termly.io/resource-blocker/support/embed.min.js.map

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

SEO

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
gtmetrix.com/blog/gtmetrix-vs-lighthouse-devtools/	Read more
gtmetrix.com/blog/gtmetrix-alternatives/	Read more

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

100

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

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.

354 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

505 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

60 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

636 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.87 s

Detailed Report

Audit breakdown by category with detailed findings.

100

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
app.termly.io/resource-blocker/fbd418dc-a86f-4230-b813-4dc2d2aa8556	14400.0 s	143.6 KiB
gtmetrix.com/static/r322/js/gtmetrix.min.js	14400.0 s	122.7 KiB
gtmetrix.com/static/r322/images/home/features-history.png	14400.0 s	88.9 KiB
gtmetrix.com/static/r322/css/gtmetrix.min.css	14400.0 s	59.3 KiB
cdn.mxpnl.com/libs/mixpanel-2-latest.min.js	600.0 s	31.5 KiB
gtmetrix.com/static/r322/images/home/features-crux.webp	14400.0 s	33.3 KiB
gtmetrix.com/static/r322/images/home/features-devices.webp	14400.0 s	32.8 KiB
gtmetrix.com/static/r322/fonts/MavenPro-medium-500.woff2	14400.0 s	23.7 KiB
gtmetrix.com/static/r322/images/home/features-alerts.webp	14400.0 s	22.3 KiB
app.termly.io/resource-blocker/support/894-6156b36a131577c56e7e.min.js	14400.0 s	8.4 KiB
gtmetrix.com/static/r322/images/bg-body.png	14400.0 s	4.9 KiB
gtmetrix.com/static/r322/images/home/logo-godaddy.png	14400.0 s	3.8 KiB
app.termly.io/resource-blocker/support/808-26e9c6c7a3bd048ed656.min.js	14400.0 s	3.2 KiB
gtmetrix.com/static/r322/images/home/logo-adobe.png	14400.0 s	2.7 KiB
app.termly.io/resource-blocker/support/524-7d36cb122791702e3df2.min.js	14400.0 s	2.7 KiB
cdn.mxpnl.com/libs/mixpanel-js-wrapper.min.js	600.0 s	1.7 KiB
app.termly.io/resource-blocker/support/377-e518d8a5c599aa1c5977.min.js	14400.0 s	873 B

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV

nodeLabel: Test your website speed GTmetrix tells you how your website performs, why it's …

path: 1,HTML,1,BODY,1,DIV,2,MAIN,0,ARTICLE,0,SECTION,0,DIV

selector: main.page-home-content > article > section.home-section-analyze > div.home-section-analyze-container

snippet: <div class="home-section-analyze-container theme-modal-btns">

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
gtmetrix.com/static/r322/css/gtmetrix.min.css	59.3 KiB	81 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Report History graph `article > section.layout-zebra-section > div.layout-zebra-section-content > img.home-img-shadow`	gtmetrix.com/static/r322/images/home/features-history.png	88.7 KiB	36.5 KiB
GTmetrix vs Lighthouse (DevTools) `div.home-section-news-container > div.card > a.home-section-news-item-img > img`	/blog/wp-content/uploads/2025/12/GTmetrix-vs-DevTools-fea...	26.7 KiB	8.6 KiB
GTmetrix Alternatives `div.home-section-news-container > div.card > a.home-section-news-item-img > img`	/blog/wp-content/uploads/2025/11/GTmetrix-Alternatives-fe...	25.8 KiB	7.7 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 343.8 KiB

URL	Transfer Size	Est Savings
gtmetrix.com/static/r322/js/gtmetrix.min.js	122.5 KiB	95.6 KiB
sst.gtmetrix.com/gtag/js?id=G-GSJLD4V4YY&cx=c&gtm=4e64h1	170.3 KiB	66.4 KiB
www.googletagmanager.com/gtag/js?id=AW-17360026842&cx=c&gtm=4e64h1	143.5 KiB	65.7 KiB
sst.gtmetrix.com/tm?origin=https://gtmetrix.com	156.8 KiB	61.6 KiB
app.termly.io/resource-blocker/fbd418dc-a86f-4230-b813-4dc2d2aa8556	143.3 KiB	54.5 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Time to Interactive 1.9 s

●Max Potential First Input Delay 100 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,377 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.5 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 4 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 190 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 180 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Get Started for Free `nav > div.user-nav > div#user-nav-signup > a.js-auth-widget-link`
We're relied on by the best, with 1,393,490,186 pages analyzed so far. `article > section.home-section-analyzed > div.home-section-analyzed-content > h2.home-section-analyzed-title`
Read more `div.card > div.home-section-news-item-content > p.home-section-news-btn > a.btn`
Read more `div.card > div.home-section-news-item-content > p.home-section-news-btn > a.btn`
Read the Blog `article > section.home-section-news > div.home-section-news-link > a.btn`
Additional Test Locations only available with GTmetrix PRO. `div.layout-zebra-section-content > div.home-content-text > p > a`

These are opportunities to improve the legibility of your content.

Navigation

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Product `div.footer-content > div.footer-links > div.footer-links-column > h6`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.page-home > div.page-wrapper > header.header > a.site-nav-home `body.page-home > div.page-wrapper > header.header > a.site-nav-home`
footer.footer > div.footer-content-wrapper > div.footer-about > a.site-nav-home `footer.footer > div.footer-content-wrapper > div.footer-about > a.site-nav-home`
body.page-home > div#menu-site-nav > a.menu-close `body.page-home > div#menu-site-nav > a.menu-close`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

100

Best Practices

General

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
sst.gtmetrix.com/gtag/js?id=G-GSJLD4V4YY&cx=c&gtm=4e64h1
app.termly.io/resource-blocker/support/894-6156b36a131577c56e7e.min.js	app.termly.io/resource-blocker/support/894-6156b36a131577c56e7e.min.js.map
app.termly.io/resource-blocker/support/808-26e9c6c7a3bd048ed656.min.js	app.termly.io/resource-blocker/support/808-26e9c6c7a3bd048ed656.min.js.map
app.termly.io/resource-blocker/support/524-7d36cb122791702e3df2.min.js	app.termly.io/resource-blocker/support/524-7d36cb122791702e3df2.min.js.map
app.termly.io/resource-blocker/support/377-e518d8a5c599aa1c5977.min.js	app.termly.io/resource-blocker/support/377-e518d8a5c599aa1c5977.min.js.map
app.termly.io/resource-blocker/fbd418dc-a86f-4230-b813-4dc2d2aa8556	app.termly.io/resource-blocker/support/embed.min.js.map

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

SEO

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
gtmetrix.com/blog/gtmetrix-vs-lighthouse-devtools/	Read more
gtmetrix.com/blog/gtmetrix-alternatives/	Read more

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://gtmetrix.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (1)

Content (3)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Navigation

Names and labels

Best practices

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Navigation

Names and labels

Best practices

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts