Skip to content
Audit Complete

Results for https://www.elegantthemes.com

Visit site
Singapore Singapore · Singapore Completed: Apr 4, 2026 16:30 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C70

Site Health

Score: 70 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

1

Content-Security-Policy header is missing

Security › Security Headers
2

HSTS header is missing

Security › Security Headers
3

No Content-Security-Policy header found

Security › Content Security Policy
4

Page weighs 7.4 MB (4.4 MB transferred)

Performance › Page Weight Budget
5

1 control(s) without accessible label

Accessibility › Form Accessibility
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.elegantthemes.com)](https://beavercheck.com/results/add77e26-6996-4f66-b444-32a5375e77b9)
<a href="https://beavercheck.com/results/add77e26-6996-4f66-b444-32a5375e77b9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.elegantthemes.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.elegantthemes.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

72
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
82
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.38 s

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

2.43 s

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

1.20 s

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

0.042

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

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

16.96 s

Detailed Report

Audit breakdown by category with detailed findings.

72

Performance

Insights

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

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:67.838 source:map[type:text value:[unattributed]]] map[reflowTime:22.871 source:map[column:3828 line:0 type:source-location url:https://www.elegantthemes.com/js/allpages-new.js?ver=6.94 urlProvider:network]]]

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

URLResource SizeEst Savings
section#divi-hero > div.grid-row > div.video-container-gradient > video.w-full section#divi-hero > div.grid-row > div.video-container-gradient > video.w-full
www.elegantthemes.com/images/divi-5/d5-builder-poster.jpg104.3 KiB97.2 KiB
Josh Hall div.testimonial-slider-container > div.testimonial-slider-slide > div.testimonial-slider-author > img
www.elegantthemes.com/images/placeholder.jpg6.1 KiB6.0 KiB
Josh Hall div.testimonial-slider-container > div.testimonial-slider-slide > div.testimonial-slider-author > img
www.elegantthemes.com/images/faces/josh-hall.jpg4.7 KiB4.5 KiB

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

lhId: page-0-VIDEO
nodeLabel: section#divi-hero > div.grid-row > div.video-container-gradient > video.w-full
path: 1,HTML,1,BODY,3,SECTION,1,DIV,0,DIV,0,VIDEO
selector: section#divi-hero > div.grid-row > div.video-container-gradient > video.w-full
snippet: <video class="w-full h-auto leading-0" width="1258" height="655" autoplay="" loop="" muted="" playsinline="" poster="/images/divi-5/d5-builder-poster.jpg">

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.

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

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

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.

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.

TTI

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 100 ms 3.3 KiB
URLTransfer SizeEst Savings
www.elegantthemes.com/js/intersectional-observer.js?ver=6.946.0 KiB3.3 KiB

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

CategoryTime Spent
Script Evaluation2.8 s
Other1.6 s
Style & Layout834 ms
Script Parsing & Compilation536 ms
Rendering379 ms
Parse HTML & CSS95 ms
Garbage Collection30 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

Failure reasonFailure type
Pages with WebSocket cannot enter back/forward cache.Pending browser support

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

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
Elegant Themes div#main-nav > div.row-container > a#logo > img
www.elegantthemes.com/images/logo-light.svg

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
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Reduce unused CSS
User Timing marks and measures 9 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 3 animated elements found
Network Requests
Network Round Trip Times 240 ms
Server Backend Latencies 110 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 30 ms
Avoid large layout shifts 9 layout shifts found
INP breakdown
82

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Failing Elements
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot

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.

Contrast

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

Failing Elements
Join 974,872 empowered web design professionals & business owners section#divi-hero > div.grid-row > div.col > h4.text-gray
Divi is for everyone section > div.grid-row > div.col > h4.text-accent
The Divi Ecosystem & Divi PRO★ section > div.grid-row > div.col > h4.text-accent
Divi Cloud section > div.grid-row > div.col > h6.text-accent

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Failing Elements
Divi Dash div.grid-row > div.col > 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.

Failing Elements
Join 974,872 empowered web design professionals & business owners section#divi-hero > div.grid-row > div.col > h4.text-gray
The ultimate theme and website building framework for WordPress section#divi-cta > div.grid-row > div.col > h4
Limitless drag & drop visual editing section.rounded-lg > div.grid-row > div.col > h4
Divi AI section > div.grid-row > div.col > h6.text-accent
Unlimited website usage div.grid-row-container > div.grid-row > div.col > h5
Facebook section#main-footer > div.grid-row > a#facebook > h6

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-prev
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-next

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html html

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
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
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
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
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
`<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
Form elements have associated labels
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
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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Uses HTTPS
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
Page has valid source maps
Redirects HTTP traffic to HTTPS
92

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.

Link destinationLink Text
www.elegantthemes.com/gallery/divi/Learn 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

96
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
82
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

681 ms

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

848 ms

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

64 ms

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

0.041

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

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

3.70 s

Detailed Report

Audit breakdown by category with detailed findings.

96

Performance

Insights

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

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:70.149 source:map[type:text value:[unattributed]]] map[reflowTime:1.737 source:map[column:1531 line:0 type:source-location url:https://www.elegantthemes.com/js/testimonial-slider.js?ver=6.94 urlProvider:network]]]

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

URLResource SizeEst Savings
section#divi-hero > div.grid-row > div.video-container-gradient > video.w-full section#divi-hero > div.grid-row > div.video-container-gradient > video.w-full
www.elegantthemes.com/images/divi-5/d5-builder-poster.jpg104.3 KiB27.7 KiB

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

lhId: page-0-VIDEO
nodeLabel: section#divi-hero > div.grid-row > div.video-container-gradient > video.w-full
path: 1,HTML,1,BODY,3,SECTION,1,DIV,0,DIV,0,VIDEO
selector: section#divi-hero > div.grid-row > div.video-container-gradient > video.w-full
snippet: <video class="w-full h-auto leading-0" width="1258" height="655" autoplay="" loop="" muted="" playsinline="" poster="/images/divi-5/d5-builder-poster.jpg">

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.

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
value: No additional origins are good candidates for preconnecting

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

RequestCache TTLTransfer Size
connect.facebook.net/en_US/fbevents.js1200.0 s95.0 KiB
www.clickcease.com/monitor/stat.js0.0 ms43.6 KiB
/signals/config/967149496645973?v=2.9.291&r=stable&domain...1200.0 s37.2 KiB
www.elegantthemes.com/images/divi-5/perspective-d5.webp604800.0 s209.2 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
amplify.outbrain.com/cp/obtp.js1200.0 s18.3 KiB
cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151607259200.0 s68.6 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
widget.trustpilot.com/trustboxes/5419b6ffb0d04a076446a9af/main.js86400.0 s26.0 KiB
a.quora.com/qevents.js14400.0 s14.7 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/625261456364/...14400.0 s13.9 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
widget.intercom.io/widget/hrpt54hy300.0 s3.6 KiB
widget.trustpilot.com/bootstrap/v5/tp.widget.bootstrap.min.js86400.0 s8.0 KiB
s.pinimg.com/ct/lib/main.34af66ec.js1209600.0 s27.6 KiB
/1431603/trc/3/json?tim=1775320187101&data=%7B%22id%22%3A...0.0 ms2.4 KiB
www.elegantthemes.com/fonts/lato/lato-v23-latin-regular.woff2604800.0 s23.2 KiB
www.elegantthemes.com/fonts/lato/lato-v23-latin-700.woff2604800.0 s22.6 KiB
www.elegantthemes.com/fonts/lato/lato-v23-latin-900.woff2604800.0 s22.1 KiB
/api/v1/sync/71d64a37-4751-4716-a267-6f7ef2b9b517/web?cal...3600.0 s2.2 KiB
ct.pinterest.com/static/ct/token_create.js7200.0 s2.2 KiB
s.pinimg.com/ct/core.js7200.0 s2.1 KiB
cdn.onesignal.com/sdks/OneSignalSDK.js259200.0 s3.6 KiB
/rp.gif?ts=1775320187156&id=t2_7v0jxedd&event=PageVisit&m...0.0 ms637 B
wave.outbrain.com/mtWavesBundler/handler/0033bb546ef38e2da393ff024b77ae96f360.0 s539 B
/collect?v=2&fmt=js&pid=3661436&time=1775320187961&li_ads...0.0 ms453 B
www.elegantthemes.com/images/placeholder.webp604800.0 s4.2 KiB
/_/ad/269de845c3d245e6b9286d6522cd81c0/pixel?j=1&u=https%...0.0 ms295 B
tr.outbrain.com/cachedClickId?marketerId=0033bb546ef38e2da393ff024b77ae96f30.0 ms293 B
/tr/?id=967149496645973&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms16 B

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.

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.

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.

Diagnostics

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

CategoryTime Spent
Script Evaluation1.0 s
Other457 ms
Style & Layout305 ms
Script Parsing & Compilation154 ms
Rendering56 ms
Parse HTML & CSS29 ms
Garbage Collection9.8 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

Failure reasonFailure type
Pages with WebSocket cannot enter back/forward cache.Pending browser support

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 0.0 ms 3.3 KiB
URLTransfer SizeEst Savings
www.elegantthemes.com/js/intersectional-observer.js?ver=6.946.0 KiB3.3 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.

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
Elegant Themes div#main-nav > div.row-container > a#logo > img
www.elegantthemes.com/images/logo-light.svg

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
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Reduce unused CSS
User Timing marks and measures 7 user timings
JavaScript execution time 0.7 s
Avoid long main-thread tasks 4 long tasks found
Avoid non-composited animations 38 animated elements found
Network Requests
Network Round Trip Times 240 ms
Server Backend Latencies 240 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 30 ms
Avoid large layout shifts 5 layout shifts found
INP breakdown
82

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Failing Elements
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot

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.

Contrast

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

Failing Elements
Divi is for everyone section > div.grid-row > div.col > h4.text-accent
The Divi Ecosystem & Divi PRO★ section > div.grid-row > div.col > h4.text-accent
Divi Cloud section > div.grid-row > div.col > h6.text-accent

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Failing Elements
Divi Quick Sites div.grid-row > div.col > p > a
Divi AI div.grid-row > div.col > p > a
pre-made layouts div.grid-row > div.col > p > a
Divi Dash div.grid-row > div.col > 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.

Failing Elements
Join 974,872 empowered web design professionals & business owners section#divi-hero > div.grid-row > div.col > h4.text-gray
The ultimate theme and website building framework for WordPress section#divi-cta > div.grid-row > div.col > h4
Limitless drag & drop visual editing section.rounded-lg > div.grid-row > div.col > h4
Divi AI section > div.grid-row > div.col > h6.text-accent
Unlimited website usage div.grid-row-container > div.grid-row > div.col > h5
Facebook section#main-footer > div.grid-row > a#facebook > h6

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-prev
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-next

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html html

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
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
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
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
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
`<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
Form elements have associated labels
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
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.
77

Best Practices

Trust and Safety

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 about responsibly getting permission for notifications.

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation 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
Page has valid source maps
Redirects HTTP traffic to HTTPS
92

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.

Link destinationLink Text
www.elegantthemes.com/gallery/divi/Learn 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`

Send Feedback