Skip to content
https://www.digitalocean.com

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.

57

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.

RequestCache TTLTransfer Size
tags.pw.adn.cloud/GCZMHM/activation.js14400.0 s42.7 KiB
/cdn-cgi/image/quality=75,width=1080/https://www.digitalo...0.0 ms25.4 KiB
www.digitalocean.com/_next/static/media/storage-in-action.680b187c.webp0.0 ms15.4 KiB
www.digitalocean.com/_next/static/media/databases-in-action.9065bde5.webp0.0 ms12.6 KiB
cdn.schemaapp.com/javascript/highlight.js0.0 ms12.1 KiB
www.digitalocean.com/_next/static/media/appplatform-in-action.2fda2505.webp0.0 ms12.0 KiB
www.digitalocean.com/_next/static/media/kubernetes-in-action.747c84a4.webp0.0 ms11.7 KiB
www.digitalocean.com/_next/static/media/richard-li.1a748efa.webp0.0 ms11.2 KiB
/notice?domain=digitalocean.com&c=teconsent&js=nj&noticeT...3600.0 s13.2 KiB
www.digitalocean.com/_next/static/media/gradientAI-in-action.49777583.webp0.0 ms9.5 KiB
www.digitalocean.com/_next/static/media/gorkem-yurtseven.68264da7.webp0.0 ms9.4 KiB
www.digitalocean.com/_next/static/media/droplets-in-action.2b7cfa84.webp0.0 ms9.4 KiB
/cdn-cgi/image/quality=75,width=1080/https://www.digitalo...0.0 ms6.7 KiB
segment.digitalocean.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js7200.0 s8.9 KiB
www.digitalocean.com/_next/static/media/matt-gray.8603a439.webp0.0 ms6.6 KiB
/cdn-cgi/image/quality=75,width=1080/https://www.digitalo...0.0 ms6.6 KiB
/cdn-cgi/image/quality=75,width=256/https://www.digitaloc...0.0 ms4.6 KiB
/cdn-cgi/image/quality=75,width=384/https://www.digitaloc...0.0 ms2.8 KiB
/cdn-cgi/image/quality=75,width=384/https://www.digitaloc...0.0 ms2.8 KiB
/cdn-cgi/image/quality=75,width=256/https://www.digitaloc...0.0 ms2.5 KiB
/cdn-cgi/image/quality=75,width=256/https://www.digitaloc...0.0 ms2.3 KiB
/cdn-cgi/image/quality=75,width=384/https://www.digitaloc...0.0 ms2.3 KiB
/cdn-cgi/image/quality=75,width=256/https://www.digitaloc...0.0 ms2.3 KiB
/cdn-cgi/image/quality=75,width=384/https://www.digitaloc...0.0 ms2.2 KiB
/cdn-cgi/image/quality=75,width=384/https://www.digitaloc...0.0 ms2.1 KiB
/next-integrations/actions/amplitude-plugins/f12a4347e108...7200.0 s2.6 KiB
/cdn-cgi/image/quality=75,width=384/https://www.digitaloc...0.0 ms2.0 KiB
/cdn-cgi/image/quality=75,width=256/https://www.digitaloc...0.0 ms1.8 KiB
/cdn-cgi/image/quality=75,width=384/https://www.digitaloc...0.0 ms1.8 KiB
/cdn-cgi/image/quality=75,width=256/https://www.digitaloc...0.0 ms1.3 KiB
/cdn-cgi/image/quality=75,width=256/https://www.digitaloc...0.0 ms1.1 KiB
/cdn-cgi/image/quality=75,width=384/https://www.digitaloc...0.0 ms1.1 KiB

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

URLResource SizeEst Savings
div.CarouselVideostyles__StyledCarousel-sc-1aj5b52-0 > ul.CarouselVideostyles__StyledCarouselSlide-sc-1aj5b52-5 > li > video div.CarouselVideostyles__StyledCarousel-sc-1aj5b52-0 > ul.CarouselVideostyles__StyledCarouselSlide-sc-1aj5b52-5 > li > video
www.digitalocean.com/_next/static/media/storage-in-action.680b187c.webp15.3 KiB6.3 KiB
div.CarouselVideostyles__StyledCarousel-sc-1aj5b52-0 > ul.CarouselVideostyles__StyledCarouselSlide-sc-1aj5b52-5 > li > video div.CarouselVideostyles__StyledCarousel-sc-1aj5b52-0 > ul.CarouselVideostyles__StyledCarouselSlide-sc-1aj5b52-5 > li > video
www.digitalocean.com/_next/static/media/databases-in-action.9065bde5.webp12.5 KiB5.1 KiB
div.CarouselVideostyles__StyledCarousel-sc-1aj5b52-0 > ul.CarouselVideostyles__StyledCarouselSlide-sc-1aj5b52-5 > li > video div.CarouselVideostyles__StyledCarousel-sc-1aj5b52-0 > ul.CarouselVideostyles__StyledCarouselSlide-sc-1aj5b52-5 > li > video
www.digitalocean.com/_next/static/media/appplatform-in-action.2fda2505.webp11.9 KiB4.8 KiB
div.CarouselVideostyles__StyledCarousel-sc-1aj5b52-0 > ul.CarouselVideostyles__StyledCarouselSlide-sc-1aj5b52-5 > li > video div.CarouselVideostyles__StyledCarousel-sc-1aj5b52-0 > ul.CarouselVideostyles__StyledCarouselSlide-sc-1aj5b52-5 > li > video
www.digitalocean.com/_next/static/media/kubernetes-in-action.747c84a4.webp11.6 KiB4.7 KiB

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-4-VIDEO
nodeLabel: div.CarouselVideostyles__StyledCarousel-sc-1aj5b52-0 > ul.CarouselVideostyles__StyledCarouselSlide-sc-1aj5b52-5 > li > video
path: 1,HTML,1,BODY,8,DIV,1,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,UL,0,LI,0,VIDEO
selector: div.CarouselVideostyles__StyledCarousel-sc-1aj5b52-0 > ul.CarouselVideostyles__StyledCarouselSlide-sc-1aj5b52-5 > li > video
snippet: <video loop="" muted="" playsinline="" poster="/_next/static/media/databases-in-action.9065bde5.webp">

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

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.

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

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
Rendering12.9 s
Other7.8 s
Script Evaluation5.3 s
Style & Layout2.6 s
Script Parsing & Compilation708 ms
Garbage Collection346 ms
Parse HTML & CSS95 ms

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.

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
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 18 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 700 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 20 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○Avoid non-composited animations
90

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Zoltan Bettenbuk CTO, ScraperAPI The cost of running ScraperAPI would be 250%… div#customers-growing-with-digitalocean > div.Sectionstyles__StyledSectionInner-sc-4l5hhw-1 > div.pages__StyledCustomerMarqueeContainer-sc-a481e4cd-3 > div.pages__StyledCustomerCardsContainer-sc-a481e4cd-2

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
div.Gridstyles-sc-isu2n3-0 > div.CarouselVideostyles__StyledCarouselNavWrapper-sc-1aj5b52-1 > div.CarouselVideostyles__StyledCarouselNav-sc-1aj5b52-2 > button.ButtonCirclestyles-sc-17yid1o-0 div.Gridstyles-sc-isu2n3-0 > div.CarouselVideostyles__StyledCarouselNavWrapper-sc-1aj5b52-1 > div.CarouselVideostyles__StyledCarouselNav-sc-1aj5b52-2 > button.ButtonCirclestyles-sc-17yid1o-0
div.Gridstyles-sc-isu2n3-0 > div.CarouselVideostyles__StyledCarouselNavWrapper-sc-1aj5b52-1 > div.CarouselVideostyles__StyledCarouselNav-sc-1aj5b52-2 > button.ButtonCirclestyles-sc-17yid1o-0 div.Gridstyles-sc-isu2n3-0 > div.CarouselVideostyles__StyledCarouselNavWrapper-sc-1aj5b52-1 > div.CarouselVideostyles__StyledCarouselNav-sc-1aj5b52-2 > button.ButtonCirclestyles-sc-17yid1o-0

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>`
●`[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
●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.
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○`<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">`
○`<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.
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
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
Access to fetch at 'https://api-ingest.pocustrack.com/v1/visitor-events/enqueue' from origin 'https://www.digitalocean.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 404 ()
Uncaught (in promise) TypeError: Failed to fetch (api-ingest.pocustrack.com)
●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 DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
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.digitalocean.com/products/gradientLearn 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