Skip to content
https://studiopress.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

87

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

Performance issues directly impact user engagement and conversion rates.

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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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-IMG
nodeLabel: Genesis Blocks Screengrab
path: 1,HTML,1,BODY,1,DIV,2,DIV,0,DIV,0,MAIN,0,ARTICLE,1,DIV,2,DIV,0,DIV,1,DIV,0,IMG
selector: div#home-cta > div.columns > div.column > img.attachment-510x510
snippet: <img width="510" height="510" src="https://www.studiopress.com/wp-content/uploads/gb-hero-image-1-600x600.png" class="attachment-510x510 size-510x510 entered lazyloaded" alt="Genesis Blocks Screengrab" decoding="async" data-lazy-srcset="https://www.studiopress.com/wp-content/uploads/gb-hero-image-1-600x600.png…" data-lazy-sizes="(max-width: 510px) 100vw, 510px" data-lazy-src="https://www.studiopress.com/wp-content/uploads/gb-hero-image-1-600x600.png" data-ll-status="loaded" sizes="(max-width: 510px) 100vw, 510px" srcset="https://www.studiopress.com/wp-content/uploads/gb-hero-image-1-600x600.png…" …>

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.

URLTransfer SizeDuration
/wp-content/themes/studiopress_2017_rt/lib/icons/sp-icons...1.3 KiB
www.studiopress.com/wp-includes/css/dist/components/style.min.css?ver=6.9.414.7 KiB
/wp-content/cache/min/1/wp-content/themes/studiopress_201...1.2 KiB
/wp-content/cache/min/1/wp-content/plugins/simple-urls/ad...2.5 KiB
/wp-content/cache/min/1/wp-content/themes/studiopress_201...4.0 KiB
www.studiopress.com/wp-includes/css/dist/patterns/style.min.css?ver=6.9.4754 B
/wp-content/cache/min/1/wp-content/plugins/wpengine-meta-...801 B
www.studiopress.com/wp-includes/css/dist/reusable-blocks/style.min.css?ver=6.9.4333 B
www.studiopress.com/wp-includes/css/dist/preferences/style.min.css?ver=6.9.4464 B
www.studiopress.com/wp-includes/css/dist/block-library/style.min.css?ver=6.9.416.0 KiB
/wp-content/cache/min/1/wp-content/themes/studiopress_201...1.1 KiB
/wp-content/cache/min/1/wp-content/themes/studiopress_201...807 B
/wp-content/cache/min/1/wp-content/themes/studiopress_201...1.0 KiB
www.studiopress.com/wp-includes/css/dist/editor/style.min.css?ver=6.9.410.3 KiB
/wp-content/cache/min/1/wp-content/plugins/studiopress-bl...240 B
/wp-content/cache/min/1/wp-content/plugins/atomic-blocks/...10.1 KiB
/wp-content/cache/min/1/wp-content/themes/studiopress_201...5.4 KiB
/wp-content/cache/min/1/wp-content/themes/studiopress_201...9.1 KiB
www.studiopress.com/wp-content/cache/min/1/vdm5rif.css?ver=1769187402525 B
www.studiopress.com/wp-includes/css/dist/block-editor/style.min.css?ver=6.9.416.8 KiB
/p.css?s=1&k=vdm5rif&ht=tk&f=2005.2006.2007.2008.2009.201...172 B203 ms

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.

RequestCache TTLTransfer Size
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
js.codedrink.com/snippet.min.js?ver=143.2026042214400.0 s65.2 KiB
/signals/config/1545550999041394?v=2.9.303&r=stable&domai...1200.0 s47.6 KiB
js.hs-analytics.net/analytics/1776889800000/298401.js300.0 s42.4 KiB
js.hs-banner.com/298401.js300.0 s18.6 KiB
/journey.js/v1/LZRMUc7x7LltRdrD3yIfYi5htRU2JU5r/journey.m...28800.0 s29.1 KiB
www.dwin1.com/19038.js600.0 s15.4 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...14400.0 s13.2 KiB
js.hsadspixel.net/pixels.js600.0 s3.9 KiB
js.hs-scripts.com/298401.js90.0 s1.0 KiB
/track.php?fingerprint=946b36c8-1e39-4c36-a6b8-c2f5254a47...0.0 ms177 B
/tr/?id=1545550999041394&ev=PageView&dl=https%3A%2F%2Fwww...0.0 ms19 B
/p.css?s=1&k=vdm5rif&ht=tk&f=2005.2006.2007.2008.2009.201...604800.0 s172 B

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.

URLResource SizeEst Savings
Genesis Blocks Screengrab div#home-cta > div.columns > div.column > img.attachment-510x510
www.studiopress.com/wp-content/uploads/gb-hero-image-1-600x600.png97.4 KiB55.1 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 604 ms
URLTime Spent
studiopress.com/257 ms
www.studiopress.com/347 ms
www.studiopress.com/0.0 ms

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

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 57.2 KiB
URLTransfer SizeEst Savings
www.studiopress.com/wp-includes/css/dist/block-editor/style.min.css?ver=6.9.416.7 KiB16.6 KiB
www.studiopress.com/wp-includes/css/dist/block-library/style.min.css?ver=6.9.415.9 KiB15.8 KiB
www.studiopress.com/wp-includes/css/dist/components/style.min.css?ver=6.9.414.6 KiB14.6 KiB
www.studiopress.com/wp-includes/css/dist/editor/style.min.css?ver=6.9.410.2 KiB10.2 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 240 ms 376.1 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtm.js?id=GTM-P9VK59Q&l=dataLayer160.4 KiB103.4 KiB
www.googletagmanager.com/gtag/destination?id=AW-997788469&cx=c&gtm=4e64k0h1133.9 KiB66.9 KiB
www.googletagmanager.com/gtag/js?id=G-QQ5FN8NX8W&cx=c&gtm=4e64k0h1165.4 KiB64.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-P9VK59Q160.5 KiB59.7 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB32.9 KiB
js.codedrink.com/snippet.min.js?ver=143.2026042264.5 KiB28.8 KiB
/wp-content/mu-plugins/wpengine-library/js/jquery-core.js...32.0 KiB20.0 KiB

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

●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 60 ms
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,457 KiB
●User Timing marks and measures 5 user timings
●JavaScript execution time 0.4 s
●Minimizes main-thread work 1.0 s
●Avoid long main-thread tasks 3 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 570 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 500 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○Avoid non-composited animations
89

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
StudioPress nav.wpe-navs__metanav-container > ul.wpe-navs__metanav__nav > li.wpe-navs__metanav__navitem > span.wpe-navs__metanav__navlink

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
div.flexible-widgets > section#nav_menu-14 > div.widget-wrap > h5.widgettitle div.flexible-widgets > section#nav_menu-14 > div.widget-wrap > h5.widgettitle

These are opportunities to improve keyboard navigation in your application.

Names and labels

Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more about alt text for `object` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wrap > div.stats > div.stat > object div.wrap > div.stats > div.stat > object
div.wrap > div.stats > div.stat > object div.wrap > div.stats > div.stat > object
div.wrap > div.stats > div.stat > object div.wrap > div.stats > div.stat > object

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.

○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>`
●`[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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Background and foreground colors have a sufficient contrast ratio
●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.
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○Buttons have an accessible name
○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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
62

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
www.studiopress.com/Allowed

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
www.studiopress.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
www.studiopress.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge
www.studiopress.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
AttributionReporting
connect.facebook.net/en_US/fbevents.js line 279, col 769
●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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.studiopress.com/genesis-pro/Read More
my.studiopress.com/themes/genesis/Learn More
my.studiopress.com/themes/Learn More
www.studiopress.com/genesis-blocks/Learn More
www.studiopress.com/genesis-custom-blocks/Learn More
www.studiopress.com/genesis-pro/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`

Send Feedback