Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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

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.

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
cdn.trustindex.io/loader.js?ver=1	0.0 ms	21.5 KiB

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
/wp-content/plugins/elementor/assets/lib/font-awesome/web...	115 ms
/wp-content/plugins/elementor/assets/lib/font-awesome/web...	115 ms
/wp-content/plugins/elementor/assets/lib/font-awesome/web...	110 ms

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:30.458 source:map[type:text value:[unattributed]]]]

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
div.elementor-element > div.elementor-widget-container > a > img.attachment-large `div.elementor-element > div.elementor-widget-container > a > img.attachment-large`	/wp-content/uploads/2021/05/395288304_10228467901421044_7...	44.5 KiB	35.9 KiB

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

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
goldsmithsrvrepairs.com/wp-content/uploads/custom-css-js/147.js?v=7731	708 B
goldsmithsrvrepairs.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	29.5 KiB	158 ms
goldsmithsrvrepairs.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.0 KiB
goldsmithsrvrepairs.com/wp-content/uploads/custom-css-js/54.css?v=6794	1.2 KiB
/wp-content/plugins/elementor/assets/lib/font-awesome/css...	700 B
/wp-content/plugins/elementor/assets/lib/font-awesome/css...	702 B
/wp-content/plugins/elementor/assets/lib/font-awesome/css...	699 B	158 ms
/wp-content/plugins/elementor/assets/lib/font-awesome/css...	12.3 KiB
/wp-content/plugins/site-reviews/assets/styles/bootstrap....	4.6 KiB
/wp-content/plugins/elementskit-lite/widgets/init/assets/...	48.2 KiB	316 ms
/wp-content/uploads/elementor/css/post-166.css?ver=177932...	1.6 KiB
/wp-content/uploads/elementor/css/post-11.css?ver=1779322342	5.5 KiB	158 ms
/wp-content/plugins/elementor-pro/assets/css/widget-flip-...	1.5 KiB
/wp-content/plugins/elementor/assets/css/widget-spacer.mi...	703 B
/wp-content/plugins/image-hover-effects-addon-for-element...	3.2 KiB
/wp-content/plugins/elementor-pro/assets/css/widget-carou...	999 B
/wp-content/plugins/elementor/assets/css/conditionals/e-s...	1.1 KiB
/wp-content/uploads/elementor/css/post-20.css?ver=1779321380	2.5 KiB
/wp-content/plugins/elementskit-lite/widgets/init/assets/...	3.2 KiB
/wp-content/plugins/elementor/assets/lib/animations/style...	519 B
/wp-content/uploads/elementor/css/post-13.css?ver=1779321380	794 B
/wp-content/plugins/elementor-pro/assets/css/widget-testi...	1.8 KiB
/wp-content/plugins/elementor-pro/assets/css/widget-form....	1.8 KiB
/wp-content/plugins/elementor/assets/lib/swiper/v8/css/sw...	4.6 KiB
/wp-content/plugins/elementor/assets/css/widget-divider.m...	1.1 KiB	158 ms
/wp-content/plugins/elementor/assets/lib/eicons/css/eleme...	4.3 KiB
/wp-content/plugins/elementor/assets/css/widget-icon-list...	1.3 KiB
/wp-content/plugins/elementor/assets/css/widget-heading.m...	542 B
/wp-content/plugins/elementor/assets/css/widget-image.min...	511 B
/wp-content/plugins/elementor/assets/css/conditionals/app...	880 B
/wp-content/plugins/elementor/assets/lib/animations/style...	530 B
/wp-content/plugins/elementor/assets/css/widget-icon-box....	772 B
/wp-content/plugins/elementor/assets/css/widget-social-ic...	1.4 KiB
goldsmithsrvrepairs.com/wp-includes/css/dashicons.min.css?ver=7.0	34.7 KiB	474 ms
/wp-content/themes/hello-elementor/assets/css/theme.css?v...	1.5 KiB
/wp-content/plugins/elementor/assets/css/frontend.min.css...	6.8 KiB	158 ms
goldsmithsrvrepairs.com/wp-content/themes/hello-elementor/style.css?ver=7.0	975 B
/wp-content/themes/hello-elementor/assets/css/header-foot...	1.6 KiB
/wp-content/themes/hello-elementor/assets/css/reset.css?v...	2.0 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: 872 ms

URL	Time Spent
goldsmithsrvrepairs.com/	870 ms
/z0f76a1d14fd21a8fb5fd0d03e0fdc3d3cedae52f?wsidchk=999976...	2.0 ms
goldsmithsrvrepairs.com/	0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.0 s

URL	Time Spent
goldsmithsrvrepairs.com/	1.1 s

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: 450 ms 104.2 KiB

URL	Transfer Size	Est Savings
/wp-content/plugins/elementskit-lite/widgets/init/assets/...	47.8 KiB	47.0 KiB
goldsmithsrvrepairs.com/wp-includes/css/dashicons.min.css?ver=7.0	34.3 KiB	34.3 KiB
/wp-content/plugins/elementor/assets/lib/font-awesome/css...	11.9 KiB	11.8 KiB
/wp-content/plugins/revslider/sr6/assets/css/rs6.css?ver=...	11.7 KiB	11.1 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: 610 ms 130.1 KiB

URL	Transfer Size	Est Savings
/wp-content/plugins/revslider/sr6/assets/js/rs6.min.js?ve...	102.1 KiB	47.4 KiB
/wp-content/plugins/revslider/sr6/assets/js/rbtools.min.j...	58.5 KiB	34.4 KiB
/wp-content/plugins/elementskit-lite/widgets/init/assets/...	34.2 KiB	26.5 KiB
/wp-content/plugins/elementor/assets/lib/swiper/v8/swiper...	37.3 KiB	21.7 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	910 ms
Other	786 ms
Style & Layout	530 ms
Parse HTML & CSS	146 ms
Rendering	119 ms
Script Parsing & Compilation	117 ms
Garbage Collection	7.3 ms

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

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 0.8 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 2 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 120 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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

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
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a`
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a`

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to content `body.home > a.skip-link`

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

●`[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

●`[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

●Elements use only permitted ARIA attributes

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

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

●Heading elements appear in a sequentially-descending order

○`[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

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

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

○Identical links have the same purpose.

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

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 URL	Request Resolution
/wp-content/uploads/elementor/google-fonts/css/barlow.css...	Blocked
/wp-content/uploads/elementor/google-fonts/css/poppins.cs...	Blocked
/wp-content/uploads/elementor/google-fonts/css/lato.css?v...	Blocked
/wp-content/uploads/elementor/google-fonts/css/opensans.c...	Blocked
/wp-content/uploads/elementor/google-fonts/css/roboto.css...	Blocked
goldsmithsrvrepairs.com/wp-content/uploads/2026/01/image2-1-rotated.jpeg	Blocked

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > img.attachment-large `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > img.attachment-large`	goldsmithsrvrepairs.com/wp-content/uploads/2026/01/image2-1-rotated.jpeg	352 x 580 (0.61)	480 x 640 (0.75)

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
goldsmithsrvrepairs.com/ line 1920, col 0	`Mixed Content: The page at 'https://goldsmithsrvrepairs.com/' was loaded over HTTPS, but requested an insecure image 'http://goldsmithsrvrepairs.com/wp-content/uploads/2026/01/image2-1-rotated.jpeg'. This request has been blocked; the content must be served over HTTPS.`
goldsmithsrvrepairs.com/ line 96, col 0	`Mixed Content: The page at 'https://goldsmithsrvrepairs.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://goldsmithsrvrepairs.com/wp-content/uploads/elementor/google-fonts/css/barlow.css?ver=1748028302'. This request has been blocked; the content must be served over HTTPS.`
goldsmithsrvrepairs.com/ line 98, col 0	`Mixed Content: The page at 'https://goldsmithsrvrepairs.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://goldsmithsrvrepairs.com/wp-content/uploads/elementor/google-fonts/css/lato.css?ver=1748028304'. This request has been blocked; the content must be served over HTTPS.`
goldsmithsrvrepairs.com/ line 99, col 0	`Mixed Content: The page at 'https://goldsmithsrvrepairs.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://goldsmithsrvrepairs.com/wp-content/uploads/elementor/google-fonts/css/opensans.css?ver=1748028312'. This request has been blocked; the content must be served over HTTPS.`
goldsmithsrvrepairs.com/ line 97, col 0	`Mixed Content: The page at 'https://goldsmithsrvrepairs.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://goldsmithsrvrepairs.com/wp-content/uploads/elementor/google-fonts/css/poppins.css?ver=1748028304'. This request has been blocked; the content must be served over HTTPS.`
goldsmithsrvrepairs.com/ line 100, col 0	`Mixed Content: The page at 'https://goldsmithsrvrepairs.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://goldsmithsrvrepairs.com/wp-content/uploads/elementor/google-fonts/css/roboto.css?ver=1751127493'. This request has been blocked; the content must be served over HTTPS.`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content

●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

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●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

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

To appear in search results, crawlers need access to your app.

○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 have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`