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.

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

value: no origins were preconnected

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

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
findly.tools/badges/findly-tools-badge-light.svg	14400.0 s	132.0 KiB
firstlook.tools/badge/badge_light.svg	14400.0 s	25.9 KiB
img.turbo0.com/badge-listed-light.svg	14400.0 s	3.7 KiB
webscore.now/api/badge/cmn61mjua000a27l8ppyfn9aq?theme=light&style=score	3600.0 s	2.0 KiB

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: 300 ms 89.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-DE4EHD4D6Q	191.8 KiB	65.7 KiB
me-mo.ro/_next/static/chunks/0~rjo7uau8~qo.js	69.2 KiB	23.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 reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
me-mo.ro/	1.4 s	61 ms	34 ms
me-mo.ro/_next/static/chunks/0~rjo7uau8~qo.js	665 ms	459 ms	27 ms
Unattributable	516 ms	35 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-DE4EHD4D6Q	467 ms	358 ms	67 ms
me-mo.ro/_next/static/chunks/0mpi_r12mw-wm.js	223 ms	197 ms	15 ms
me-mo.ro/_next/static/chunks/0r6wtbcr.1j1y.js	139 ms	107 ms	6.0 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	1.3 s
Other	1.1 s
Style & Layout	433 ms
Rendering	403 ms
Script Parsing & Compilation	180 ms
Parse HTML & CSS	67 ms
Garbage Collection	28 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 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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.5 KiB

URL	Transfer Size	Est Savings
repora.ro/beacon.js	7.0 KiB	3.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Memo - Featured on Startup Fame `div.featured-marquee__track > div.featured-marquee__item > a > img`	startupfa.me/badges/featured/default.webp
Memo - Featured on Startup Fame `div.featured-marquee__track > div.featured-marquee__item > a > img`	startupfa.me/badges/featured/default.webp
Listed on Turbo0 `div.featured-marquee__track > div.featured-marquee__item > a > img`	img.turbo0.com/badge-listed-light.svg
Listed on Turbo0 `div.featured-marquee__track > div.featured-marquee__item > a > img`	img.turbo0.com/badge-listed-light.svg
Featured `div.featured-marquee__track > div.featured-marquee__item > a > img`	startupdirectory.net/badge/featured-light.svg
Featured `div.featured-marquee__track > div.featured-marquee__item > a > img`	startupdirectory.net/badge/featured-light.svg
WebScore Trust Badge `div.featured-marquee__track > div.featured-marquee__item > a > img`	webscore.now/api/badge/cmn61mjua000a27l8ppyfn9aq?theme=light&style=score
WebScore Trust Badge `div.featured-marquee__track > div.featured-marquee__item > a > img`	webscore.now/api/badge/cmn61mjua000a27l8ppyfn9aq?theme=light&style=score
Featured on toolfame.com `div.featured-marquee__track > div.featured-marquee__item > a > img`	toolfame.com/badge-light.svg
Featured on toolfame.com `div.featured-marquee__track > div.featured-marquee__item > a > img`	toolfame.com/badge-light.svg

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

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

●Avoids enormous network payloads Total size was 954 KiB

●Avoid long main-thread tasks 7 long tasks found

●Avoid non-composited animations 2 animated elements found

●Network Requests

●Network Round Trip Times 50 ms

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid large layout shifts

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

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
Scan to open Memo `div.lg:col-span-5 > div.relative > div.absolute > div.w-[140px]`

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.

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
new photo `div.relative > div.absolute > div.min-w-0 > div.text-[10px]`
01 `div.container > div.grid > div.relative > div.text-7xl`
60 SECONDS `div.container > div.grid > div.relative > div.text-xs`
02 `div.container > div.grid > div.relative > div.text-7xl`
5 MINUTES `div.container > div.grid > div.relative > div.text-xs`
03 `div.container > div.grid > div.relative > div.text-7xl`
ZERO EFFORT `div.container > div.grid > div.relative > div.text-xs`

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]` values are valid

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

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

●Buttons have an accessible name

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

●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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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.

○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

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

Source	Description
www.googletagmanager.com/gtag/js?id=G-DE4EHD4D6Q line 645, col 33	Connecting to 'https://pagead2.googlesyndication.com/ccm/collect?rcb=4&frm=0&apvc=1&tid=AW-993891724&en=page_view&dl=https%3A%2F%2Fme-mo.ro%2F&scrsrc=www.googletagmanager.com&rnd=1154317932.1792166046&navt=n&npa=1&gtm=45je6af0h2v9222113028za208zd9222113028xecxf1&gcs=G100&gcd=13p3p3V2p5l1&dma_cps=-&dma=1&tag_exp=115938465~115938469~118897920~118897930~120213116~120385423~120469145~120469153~121246026~121246034&tft=1792166045731&tfd=616&tids=AW-993891724&fmt=8' violates the following Content Security Policy directive: "connect-src 'self' https://www.googletagmanager.com https://.google-analytics.com https://.r2.cloudflarestorage.com https://cdn.me-mo.ro https://repora.ro". The action has been blocked.
www.googletagmanager.com/gtag/js?id=G-DE4EHD4D6Q line 645, col 33	Fetch API cannot load https://pagead2.googlesyndication.com/ccm/collect?rcb=4&frm=0&apvc=1&tid=AW-993891724&en=page_view&dl=https%3A%2F%2Fme-mo.ro%2F&scrsrc=www.googletagmanager.com&rnd=1154317932.1792166046&navt=n&npa=1&gtm=45je6af0h2v9222113028za208zd9222113028xecxf1&gcs=G100&gcd=13p3p3V2p5l1&dma_cps=-&dma=1&tag_exp=115938465~115938469~118897920~118897930~120213116~120385423~120469145~120469153~121246026~121246034&tft=1792166045731&tfd=616&tids=AW-993891724&fmt=8. Refused to connect because it violates the document's Content Security Policy.

www.googletagmanager.com/gtag/js?id=G-DE4EHD4D6Q line 645, col 33

Connecting to 'https://pagead2.googlesyndication.com/ccm/collect?rcb=4&frm=0&apvc=1&tid=AW-993891724&en=page_view&dl=https%3A%2F%2Fme-mo.ro%2F&scrsrc=www.googletagmanager.com&rnd=1154317932.1792166046&navt=n&npa=1&gtm=45je6af0h2v9222113028za208zd9222113028xecxf1&gcs=G100&gcd=13p3p3V2p5l1&dma_cps=-&dma=1&tag_exp=115938465~115938469~118897920~118897930~120213116~120385423~120469145~120469153~121246026~121246034&tft=1792166045731&tfd=616&tids=AW-993891724&fmt=8' violates the following Content Security Policy directive: "connect-src 'self' https://www.googletagmanager.com https://*.google-analytics.com https://*.r2.cloudflarestorage.com https://cdn.me-mo.ro https://repora.ro". The action has been blocked.

www.googletagmanager.com/gtag/js?id=G-DE4EHD4D6Q line 645, col 33

Fetch API cannot load https://pagead2.googlesyndication.com/ccm/collect?rcb=4&frm=0&apvc=1&tid=AW-993891724&en=page_view&dl=https%3A%2F%2Fme-mo.ro%2F&scrsrc=www.googletagmanager.com&rnd=1154317932.1792166046&navt=n&npa=1&gtm=45je6af0h2v9222113028za208zd9222113028xecxf1&gcs=G100&gcd=13p3p3V2p5l1&dma_cps=-&dma=1&tag_exp=115938465~115938469~118897920~118897930~120213116~120385423~120469145~120469153~121246026~121246034&tft=1792166045731&tfd=616&tids=AW-993891724&fmt=8. Refused to connect because it violates the document's Content Security Policy.

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
Content security policy

●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

●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

●Page has valid source maps

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