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 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:52.96 source:map[type:text value:[unattributed]]]]

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: A smartphone with a Surfshark logo inside a teal jelly cake, with raspberries a…

path: 1,HTML,1,BODY,6,DIV,0,DIV,1,MAIN,0,SECTION,0,DIV,0,DIV,1,DIV,0,IMG

selector: div._8BkFQ > div._pet5f > div._eEmo9 > img._47ff0

snippet: <img alt="A smartphone with a Surfshark logo inside a teal jelly cake, with raspberr…" loading="eager" width="568" height="568" decoding="async" data-nimg="1" class="_47ff0" style="color:transparent" srcset="/website/_next/image?url=/website/_next/public/_shared/images/birthday/her…" src="https://surfshark.com/website/_next/image?url=/website/_next/public/_share…">

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
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/signals/config/1690077554448261?v=2.9.303&r=stable&domai...	1200.0 s	59.8 KiB
collector-52277.us.tvsquared.com/tv2track.js	600.0 s	8.7 KiB
/d/latest/e/index.js?cu=https://d.surfshark.com/internal/...	604800.0 s	7.8 KiB
/tv2track.php?action_name=Surfshark%20VPN%20%26%20all-in-...	0.0 ms	276 B
/tr/?id=1690077554448261&ev=PageView&dl=https%3A%2F%2Fsur...	0.0 ms	19 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.

	URL	Resource Size	Est Savings
A smiling woman with glasses and curly hair looking down at her tablet `div._WReJg > div._MOSY0 > div._uChkQ > img._SJjOb`	/website/_next/image?url=/website/_next/public/_shared/im...	128.5 KiB	101.7 KiB
A smartphone with a Surfshark logo inside a teal jelly cake, with raspberries a… `div._8BkFQ > div._pet5f > div._eEmo9 > img._47ff0`	/website/_next/image?url=/website/_next/public/_shared/im...	70.2 KiB	57.0 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 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: 190 ms 271.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-N9ZV87V	160.4 KiB	59.8 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js	105.4 KiB	57.0 KiB
www.googletagmanager.com/gtag/js?id=AW-800656454&cx=c&gtm=4e64k1	155.7 KiB	52.9 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	34.8 KiB
/signals/config/1690077554448261?v=2.9.303&r=stable&domai...	59.6 KiB	23.5 KiB
surfshark.com/website/_next/static/chunks/framework-45926255fd5ae142.js	58.3 KiB	22.5 KiB
surfshark.com/website/_next/static/chunks/main-5cfc65f1b268bf47.js	39.7 KiB	20.9 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
surfshark.com/website/_next/static/chunks/framework-45926255fd5ae142.js	1.2 s	1.1 s	32 ms
www.googletagmanager.com/gtm.js?id=GTM-N9ZV87V	752 ms	617 ms	88 ms
Unattributable	684 ms	109 ms	0.0 ms
surfshark.com/	569 ms	33 ms	2.2 ms
www.googletagmanager.com/gtag/js?id=AW-800656454&cx=c&gtm=4e64k1	458 ms	392 ms	59 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js	260 ms	197 ms	57 ms
connect.facebook.net/en_US/fbevents.js	169 ms	123 ms	44 ms
surfshark.com/website/_next/static/chunks/main-5cfc65f1b268bf47.js	148 ms	120 ms	18 ms
/d/latest/e/index.js?cu=https://d.surfshark.com/internal/...	148 ms	112 ms	29 ms
/signals/config/1690077554448261?v=2.9.303&r=stable&domai...	139 ms	110 ms	28 ms
surfshark.com/website/_next/static/chunks/pages/_app-2eebe5ec80bc3605.js	108 ms	76 ms	26 ms
surfshark.com/website/_next/static/chunks/pages/index-2eb90134a0a99182.js	87 ms	84 ms	2.3 ms
cdn.surfshark.com/npm/@snowplow/javascript-tracker/dist/sp.min.js	82 ms	63 ms	10 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js	54 ms	34 ms	19 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	3.2 s
Other	742 ms
Script Parsing & Compilation	472 ms
Style & Layout	261 ms
Rendering	167 ms
Parse HTML & CSS	87 ms
Garbage Collection	75 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

●Network dependency tree

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●User Timing marks and measures 13 user timings

●Avoid long main-thread tasks 19 long tasks found

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

●Network Requests

●Network Round Trip Times 130 ms

●Server Backend Latencies 190 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We love Surfshark because it is an easy-to-use app that you can download on all… `div._pet5f > div._eEmo9 > div._0FMH1 > div._6BvVF`

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
Rating: 4.5 out of 5 `div._6tMnV > div._UTQWE > div._uCQHE > div._cJz65`
Rating: 4.5 out of 5 `div._6tMnV > div._UTQWE > div._uCQHE > div._cJz65`

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.

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
MAX & OCCY `div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-MAX & OCCY`
MRWHOSETHEBOSS `div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-MRWHOSETHEBOSS`
THE TECH CHAP `div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-THE TECH CHAP`
ROSE AND ROSIE `div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-ROSE AND ROSIE`
MARCUS HOUSE `div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-MARCUS HOUSE`

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
Get Surfshark `div._XIYxa > div._7Rqyj > a._fZX0c > span._SzDTn`
Get Surfshark VPN `div._eEmo9 > div._TOdK4 > a._fZX0c > span._SzDTn`

These are opportunities to improve the legibility of your content.

○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]`s are contained by their required parent element

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

●Select elements have associated label elements.

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

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

●Document has a `<title>` element

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

○`[accesskey]` values are unique

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

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

○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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○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

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 / Warning	Source
AttributionReporting	www.googletagmanager.com/gtag/js?id=AW-800656454&cx=c&gtm=4e64k1 line 594, col 244

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
surfshark.com/api/v1/product/campaigns/active/countries/BR?coupon=undefined	`Failed to load resource: the server responded with a status of 404 ()`

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

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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`