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
laravelnews.s3.amazonaws.com/featured-images/laravel-pdf-v2-featured.png	0.0 ms	1.0 MiB
laravelnews.s3.amazonaws.com/featured-images/API-Skills-for-Laravel-LN.png	0.0 ms	713.0 KiB
laravel-news.com/build/assets/app-320c6c7a.js	7200.0 s	156.0 KiB
laravel-news.com/build/assets/app-f0901d34.css	7200.0 s	13.0 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...	14400.0 s	12.3 KiB
/p.css?s=1&k=rgt0rac&ht=tk&f=24735.24741.24736.24737.2474...	604800.0 s	172 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
div.flex > div.aspect-[2/1] > a > img.rounded-t `div.flex > div.aspect-[2/1] > a > img.rounded-t`	laravelnews.s3.amazonaws.com/featured-images/laravel-pdf-v2-featured.png	1.0 MiB	1016.2 KiB
An Opinionated Agent Skill for Building REST APIs in Laravel `div.flex > div.aspect-[2/1] > a > img.h-full`	laravelnews.s3.amazonaws.com/featured-images/API-Skills-for-Laravel-LN.png	712.6 KiB	679.9 KiB
An Opinionated Agent Skill for Building REST APIs in Laravel image `div.mt-12 > div.group > div.aspect-[2/1] > img.h-full`	/https://laravelnews.s3.amazonaws.com/featured-images/API...	53.0 KiB	48.5 KiB
Laravel Cloud is here! Zero-config managed infrastructure for Laravel apps. ima… `div.mt-12 > div.group > div.aspect-[2/1] > img.h-full`	/https://laravelnews.s3.amazonaws.com/featured-images/lar...	51.3 KiB	48.0 KiB
Attach PDFs Directly to Mailables in laravel-pdf 2.6.0 image `div.mt-12 > div.group > div.aspect-[2/1] > img.h-full`	/https://laravelnews.s3.amazonaws.com/featured-images/lar...	44.4 KiB	40.7 KiB
Get expert guidance in a few days with a Laravel code review image `div.mt-12 > div.group > div.aspect-[2/1] > img.h-full`	/https://laravelnews.s3.amazonaws.com/partners/featured_i...	41.0 KiB	37.6 KiB
Launch Your Dream SaaS Application with SaaSykit image `div.mt-12 > div.group > div.aspect-[2/1] > img.h-full`	/https://laravelnews.s3.amazonaws.com/featured-images/saa...	29.7 KiB	27.2 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-0-IMG

nodeLabel: div.flex > div.aspect-[2/1] > a > img.rounded-t

path: 1,HTML,1,BODY,2,DIV,0,DIV,4,SECTION,1,DIV,0,DIV,3,DIV,1,DIV,4,DIV,0,DIV,1,DIV,0,A,0,IMG

selector: div.flex > div.aspect-[2/1] > a > img.rounded-t

snippet: <img src="https://laravelnews.s3.amazonaws.com/featured-images/laravel-pdf-v2-featur…" class="rounded-t object-cover w-full h-full" alt="">

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

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
use.typekit.net/rgt0rac.css	1.2 KiB	755 ms
fonts.bunny.net/css?family=jetbrains-mono:400,400i	1.4 KiB	831 ms
/p.css?s=1&k=rgt0rac&ht=tk&f=24735.24741.24736.24737.2474...	172 B	751 ms

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
use.typekit.net/af/b86f1b/00000000000000007735f525/30/l?subset_id=2&fvd=n5&v=3	5.0 ms
/af/716155/00000000000000007735dd24/30/l?primer=7cdcb44be...	5.0 ms

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

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

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.

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: 980 ms 182.7 KiB

URL	Transfer Size	Est Savings
laravel-news.com/build/assets/app-320c6c7a.js	155.6 KiB	115.9 KiB
www.googletagmanager.com/gtag/js?id=G-LE9GHTERHJ	176.8 KiB	66.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.

Category	Time Spent
Other	886 ms
Script Evaluation	823 ms
Style & Layout	403 ms
Rendering	218 ms
Script Parsing & Compilation	67 ms
Parse HTML & CSS	44 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

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: 0.0 ms 10.8 KiB

URL	Transfer Size	Est Savings
laravel-news.com/build/assets/app-f0901d34.css	12.7 KiB	10.8 KiB

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,447 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.9 s

●Avoid long main-thread tasks 7 long tasks found

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

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 260 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 550 ms

●Avoid large layout shifts 1 layout shift 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.

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
Polyscope - The agent-first dev environment for Laravel `div.shadow-card > div > p > a`
Laravel Packages `div.flex > div.flex > div.pt-4 > span.text-red-600`
News `div.flex > div.flex > div.pt-3 > span.text-red-600`
View All Links→ `div.flex > div.border > div.px-3 > a.inline-flex`
View All Jobs → `div.relative > div.px-3 > div > a.inline-flex`
Post a Job → `div.relative > div.px-3 > div > a.inline-flex`
Join free `div > form > div.flex > button.inline-flex`
View all → `section.py-20 > div.mx-auto > div.flex > a.inline-flex`
View all → `section.py-32 > div.mx-auto > div.flex > a.inline-flex`
Join free `div > form > div.flex > button.inline-flex`

These are opportunities to improve the legibility of your content.

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.flex > div.flex > div.aspect-[2/1] > a `div.flex > div.flex > div.aspect-[2/1] > a`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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

○Links are distinguishable without relying on color.

○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

○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

○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
SharedStorage	laravel-news.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	laravel-news.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	laravel-news.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

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
laravel-news.com/a/script.js	`Failed to load resource: the server responded with a status of 404 ()`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
laravel-news.com/build/assets/app-320c6c7a.js

●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 DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`