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
/pagead/managed/js/adsense/m202604210101/show_ads_impl_fy...	1209600.0 s	177.2 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
follow.it/images/Facebook-logo.png	14400.0 s	1.8 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:109.08 source:map[type:text value:[unattributed]]] map[reflowTime:0.288 source:map[column:211542 line:24 type:source-location url:https://follow.it/_nuxt/iofpdxf7.js urlProvider:network]]]

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
Find Feed `div.sub-section > div.image-part > picture > img.w-full`	follow.it/_ipx/f_avif/images/Homepage/2x/find-feed.png	109.5 KiB	103.1 KiB
Set Filters `div.sub-section > div.image-part > picture > img.w-full`	follow.it/_ipx/f_avif/images/Homepage/2x/set-filters.png	105.8 KiB	97.0 KiB
Delivery Channels `div.sub-section > div.reversed-part > picture > img.w-full`	follow.it/_ipx/f_avif/images/Homepage/2x/delivery-channels.png	81.3 KiB	72.4 KiB
Get Alerts `div.sub-section > div.reversed-part > picture > img.w-full`	follow.it/_ipx/f_avif/images/Homepage/2x/get-alerts.png	64.0 KiB	56.5 KiB
Read Stories `div.readers-card > div.readers-card-image > picture > img`	follow.it/_ipx/f_avif/images/Homepage/2x/read-stories.png	16.5 KiB	15.8 KiB

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
follow.it/_nuxt/entry.wzs8Xm92.css	65.4 KiB
follow.it/_nuxt/SocialLinksAndControls.vS4ucu0q.css	890 B
follow.it/_nuxt/FitButton.CbbdC-U7.css	997 B
follow.it/_nuxt/monetization.DlDlKMeN.css	1.8 KiB
follow.it/_nuxt/FitSelect.BjheBp7o.css	789 B
follow.it/_nuxt/Footer.BvP0R_M7.css	1.3 KiB
follow.it/_nuxt/LocalizationPopover.BKOw-U8c.css	641 B
follow.it/_nuxt/FeatureNotAvailable.CtKtHsYw.css	425 B
follow.it/_nuxt/FitInput.CSeq8CJ0.css	2.2 KiB
follow.it/_nuxt/section-image.BPcO9C1x.css	470 B
follow.it/_nuxt/FitTooltip.RrdBfXaR.css	1014 B
follow.it/_nuxt/IconProvider.t81wSa1z.css	474 B

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

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.

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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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.

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.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
Navigation was cancelled before the page could be restored from back/forward cache.	Not actionable

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
follow.it/_nuxt/iofpdxf7.js	2.1 s	1.2 s	3.4 ms
follow.it/	1.7 s	329 ms	5.3 ms
Unattributable	1.6 s	898 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-Y8Q40X6HV8&cx=c&gtm=4e64k1h2	226 ms	188 ms	37 ms
www.googletagmanager.com/gtag/js?id=G-G28TLQK11C&cx=c&_slc=1	226 ms	183 ms	41 ms
/pagead/managed/js/adsense/m202604210101/show_ads_impl_fy...	213 ms	159 ms	49 ms
www.googletagmanager.com/gtm.js?id=GTM-KDHXH6Z	173 ms	139 ms	32 ms
follow.it/_nuxt/SKLau12h.js	120 ms	0.0 ms	0.1 ms
accounts.google.com/gsi/client	100 ms	76 ms	23 ms
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	83 ms	71 ms	10 ms
follow.it/_nuxt/entry.wzs8Xm92.css	73 ms	0.0 ms	0.0 ms
www.google-analytics.com/analytics.js	61 ms	51 ms	5.5 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.4 s
Other	1.8 s
Style & Layout	1.3 s
Rendering	348 ms
Script Parsing & Compilation	242 ms
Parse HTML & CSS	222 ms
Garbage Collection	32 ms

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
Get Alerts `div.sub-section > div.reversed-part > picture > img.w-full`	follow.it/_ipx/f_avif/images/Homepage/2x/get-alerts.png
Delivery Channels `div.sub-section > div.reversed-part > picture > img.w-full`	follow.it/_ipx/f_avif/images/Homepage/2x/delivery-channels.png
Set Filters `div.sub-section > div.image-part > picture > img.w-full`	follow.it/_ipx/f_avif/images/Homepage/2x/set-filters.png
Find Feed `div.sub-section > div.image-part > picture > img.w-full`	follow.it/_ipx/f_avif/images/Homepage/2x/find-feed.png
Publish Feed `div.publishers-card > div.readers-card-image > picture > img`	follow.it/_ipx/f_avif/images/Homepage/2x/publish-feed.png
Read Stories `div.readers-card > div.readers-card-image > picture > img`	follow.it/_ipx/f_avif/images/Homepage/2x/read-stories.png
Traffic `section.sub-section > div.image-part > picture > img.w-full`
Monetize Your Feeds `section.sub-section > div.reversed-part > picture > img.w-full`

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

●Modern HTTP

●Network dependency tree

●Optimize viewport for mobile

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

●User Timing marks and measures 10 user timings

●Avoid non-composited animations 2 animated elements found

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 50 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP breakdown

○LCP request discovery

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

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
Find feeds to follow `section.section-action > div.fit-button-wrapper > a.fit-button > span`
See intro `section.sub-section > div.text-part > a.see-intro > div.fit-text`
Websites using follow.it `footer.layout-footer > section.layout-footer__stats > div.layout-footer__stats__group > span.font-semibold`
Active followers `footer.layout-footer > section.layout-footer__stats > div.layout-footer__stats__group > span.font-semibold`
Feeds tracked `footer.layout-footer > section.layout-footer__stats > div.layout-footer__stats__group > span.font-semibold`
Sign up `div.layout-footer__links__group > ul.flex > li.font-medium > a.router-link-active`
Copyright © 2017-2026 Inisev Ltd. `section.layout-footer__links > div.flex > p.text-fit-blueish-gray > span`

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Elements with visible text labels have matching accessible names.

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

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

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

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

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

100

Best Practices

General

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
follow.it/_nuxt/iofpdxf7.js

●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 browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
3	`Content-Usage: bots=y, train-ai=n`	`Unknown directive`

To appear in search results, crawlers need access to your app.

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`