Skip to content
https://toprankalliance.shop

Lighthouse Mobile

· 0 checks — Mobile 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.

74

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.

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.

URLEst Savings
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/webfonts/fa-brands-400.woff260 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/webfonts/fa-solid-900.woff250 ms

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.

URLTransfer SizeDuration
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/css/all.min.css19.0 KiB934 ms
rankzly.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js1.0 KiB

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
rankzly.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js172795.0 s1.0 KiB

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

Why this matters

Performance issues directly impact user engagement and conversion rates.
head > meta head > meta

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: 813 ms
URLTime Spent
toprankalliance.shop/813 ms
rankzly.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: 150 ms 17.8 KiB
URLTransfer SizeEst Savings
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/css/all.min.css18.3 KiB17.8 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.

CategoryTime Spent
Style & Layout1.0 s
Rendering818 ms
Other333 ms
Script Evaluation48 ms
Parse HTML & CSS35 ms
Script Parsing & Compilation3.2 ms

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 294 KiB
●JavaScript execution time 0.0 s
●Avoid long main-thread tasks 3 long tasks found
●Avoid non-composited animations 72 animated elements 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 40 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 40 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
80

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section#guest-posts > div.container > div.search-bar > button section#guest-posts > div.container > div.search-bar > button

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
View Plans body > section.hero > div.container > button.cta-button
DR div.container > div.metric-detail > div.metric-header > div.metric-logo
POPULAR div.pricing-block > div.pricing-grid > div.price-card > span.popular-badge
DR 30 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
DR 40 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
DR 50 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
DR 60 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
DR 70 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
DR 75 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
PREMIUM div.pricing-block > div.pricing-grid > div.price-card > span.popular-badge
DR 80 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
DR 85 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
DA div.container > div.metric-detail > div.metric-header > div.metric-logo
DA 10 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
POPULAR div.pricing-block > div.pricing-grid > div.price-card > span.popular-badge
DA 20 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
DA 30 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
DA 40 div.pricing-block > div.pricing-grid > div.price-card > div.metric-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
POPULAR div.pricing-block > div.pricing-grid > div.price-card > span.popular-badge
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
Place Order div.pricing-grid > div.price-card > div.order-row > button.cta-button
$15 tbody > tr > td > span.pbn-price
Order tbody > tr > td > button.cta-button
$30 tbody > tr > td > span.pbn-price
Order tbody > tr > td > button.cta-button
$45 tbody > tr > td > span.pbn-price
Order tbody > tr > td > button.cta-button
$75 tbody > tr > td > span.pbn-price
Order tbody > tr > td > button.cta-button
$150 tbody > tr > td > span.pbn-price
Order tbody > tr > td > button.cta-button
$300 tbody > tr > td > span.pbn-price
Order tbody > tr > td > button.cta-button
$450 tbody > tr > td > span.pbn-price
Order tbody > tr > td > button.cta-button
$750 tbody > tr > td > span.pbn-price
Order tbody > tr > td > button.cta-button
$1,500 tbody > tr > td > span.pbn-price
Order tbody > tr > td > button.cta-button
Place Order (Selected) div.gp-wrap > div.gp-head > div.right > button.cta-button
WhatsApp Order div.gp-wrap > div.bulk-bar > div.actions > button.cta-button

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
Why Clients Prefer Our DR Service: div.metric-content > div.metric-description > div.metric-advantages > h3
Why Clients Prefer Our DA Service: div.metric-content > div.metric-description > div.metric-advantages > h3
Why Clients Prefer Our TF Service: div.metric-content > div.metric-description > div.metric-advantages > h3
Bank Transfer div.container > div.payment-grid > div.payment-card > h4

These are opportunities to improve keyboard navigation in your application.

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

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Website Niche Metrics Traffic Price te***ch.com ID: GP-001 Technology DR 9… div.container > div.gp-wrap > div > table.gp-table
○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
●Form elements have associated labels
●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
●`<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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[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.
○Image elements have `[alt]` attributes
○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.
○No element has a `[tabindex]` value greater than 0
○`<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.
96

Best Practices

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.

SourceDescription
rankzly.com/favicon.ico
Failed to load resource: the server responded with a status of 404 ()
●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 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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
100

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.

○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
●robots.txt is valid
●Document has a valid `hreflang`
○Image elements have `[alt]` attributes
○Document has a valid `rel=canonical`

Send Feedback