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
assets.mailerlite.com/jsonp/2/forms?callback=ml.fn.renderPopupsAndPromotions	180.0 s	54.3 KiB
/uc.js?cbid=98891d86-5248-4450-b742-403ae1bfec1a&implemen...	827.0 s	35.7 KiB
mailerlite.com/tag/gtm.js?id=GTM-KKG2Q6R	432000.0 s	179.7 KiB
/img/containers/assets/site/home-hero/newsletter-primary....	432000.0 s	93.2 KiB
storage.googleapis.com/mailerlite-website-bucket/logos/emailtooltester.svg	3600.0 s	10.5 KiB
www.mailerlite.com/build/assets/site-d8c0cfa3.js	432000.0 s	27.8 KiB
/img/containers/assets/gradients/02.jpg/84bc260ab00cb5f94...	432000.0 s	19.4 KiB
assets.mailerlite.com/js/universal.js	432000.0 s	14.0 KiB
cdn.jsdelivr.net/npm/@growthbook/growthbook/dist/bundles/auto.min.js	604800.0 s	16.7 KiB
assets.mlcdn.com/ml/assets/js/EHawkTalon.js	691200.0 s	14.0 KiB
storage.googleapis.com/mailerlite-website-bucket/logos/g2_logo-1718892154.svg	3600.0 s	1.7 KiB
storage.googleapis.com/mailerlite-website-bucket/logos/g2_logo.svg	3600.0 s	1.4 KiB
storage.googleapis.com/mailerlite-website-bucket/logos/getapp-logo.svg	86400.0 s	1.9 KiB
storage.googleapis.com/mailerlite-website-bucket/logos/trustradius-logo.svg	86400.0 s	1.8 KiB
www.mailerlite.com/build/assets/traffic-41633c23.js	432000.0 s	1.7 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB
assets.mailerlite.com/css/universal.css	432000.0 s	674 B
www.mailerlite.com/build/assets/_commonjsHelpers-725317a4.js	432000.0 s	220 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	40 ms

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

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.-mx-8 > div.w-full > div.bg-neutral-300 > img.w-full `div.-mx-8 > div.w-full > div.bg-neutral-300 > img.w-full`	/img/containers/assets/site/home-hero/newsletter-primary....	92.9 KiB	62.6 KiB

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

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.

Estimated savings: 881 ms

URL	Time Spent
mailerlite.com/	881 ms
www.mailerlite.com/	0.0 ms

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

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
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	668 ms	570 ms	68 ms
www.mailerlite.com/	498 ms	20 ms	5.4 ms
Unattributable	493 ms	9.7 ms	0.0 ms
/98891d86-5248-4450-b742-403ae1bfec1a/cc.js?renew=false&r...	445 ms	175 ms	31 ms
mailerlite.com/tag/gtm.js?id=GTM-KKG2Q6R	421 ms	355 ms	54 ms
/tag/gtag/js?id=G-CLV4Y1FYZL&cx=c&gtm=4e64h1&sign=db9885e...	309 ms	262 ms	46 ms
/gtag/js?id=G-QDC79JE3K2&cx=c&gtm=4e64h1&sign=db9885ec7c0...	243 ms	196 ms	45 ms
/uc.js?cbid=98891d86-5248-4450-b742-403ae1bfec1a&implemen...	206 ms	188 ms	8.7 ms
www.mailerlite.com/build/assets/site-d8c0cfa3.js	194 ms	173 ms	0.5 ms
cdn.jsdelivr.net/npm/@growthbook/growthbook/dist/bundles/auto.min.js	156 ms	140 ms	5.6 ms
assets.mailerlite.com/jsonp/2/forms?callback=ml.fn.renderPopupsAndPromotions	152 ms	4.9 ms	146 ms
www.googletagmanager.com/gtag/destination?id=AW-962313338&cx=c&gtm=4e64h1	141 ms	111 ms	29 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	2.3 s
Other	598 ms
Script Parsing & Compilation	451 ms
Parse HTML & CSS	289 ms
Style & Layout	272 ms
Garbage Collection	76 ms
Rendering	74 ms

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 23.9 KiB

URL	Transfer Size	Est Savings
www.mailerlite.com/build/assets/site-77603b85.css	26.3 KiB	23.9 KiB

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

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	177.1 KiB
/gtag/js?id=G-QDC79JE3K2&cx=c&gtm=4e64h1&sign=db9885ec7c0...	173.4 KiB	69.7 KiB
www.googletagmanager.com/gtag/destination?id=AW-962313338&cx=c&gtm=4e64h1	138.6 KiB	68.6 KiB
/tag/gtag/js?id=G-CLV4Y1FYZL&cx=c&gtm=4e64h1&sign=db9885e...	163.6 KiB	64.1 KiB
mailerlite.com/tag/gtm.js?id=GTM-KKG2Q6R	179.6 KiB	61.0 KiB
/98891d86-5248-4450-b742-403ae1bfec1a/cc.js?renew=false&r...	103.0 KiB	35.4 KiB
/uc.js?cbid=98891d86-5248-4450-b742-403ae1bfec1a&implemen...	35.5 KiB	22.4 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 17 long tasks found

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

●Page didn't prevent back/forward cache restoration

●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

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
By clicking “Accept all cookies”, you agree to the storing of cookies on your d… `body.overflow-y-auto > div#CookieBanner > div#CookieBannerNotice`

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
Accept all cookies `div.cookiebanner__main > div.cookiebanner__main__inner > div.cookiebanner__buttons > button#CybotCookiebotDialogBodyLevelButtonLevelOptinAllowAll`
Sign up free `div.flex > div.flex > div.w-full > a.type-primary`
Watch demo `div.flex > div.flex > div.w-full > a.type-black-outline`
Get a free 14-day trial of premium features \| No credit card required `div.mx-auto > div.flex > div.flex > span.text-sm`
14-day `div.flex > div.flex > span.text-sm > span.premium-days`
always available `div.text-center > div.grid > div.flex > span.opacity-50`
satisfaction rate `div.text-center > div.grid > div.flex > span.opacity-50`
avg. response time on live chat `div.text-center > div.grid > div.col-span-2 > span.opacity-50`
PRODUCT `div.container > div.grid > div > span.uppercase`
SUPPORT `div.container > div.grid > div > span.uppercase`
COMPANY `div.container > div.grid > div > span.uppercase`
For more details, review our Privacy Policy. `div.col-span-2 > div.ml-form-embedContainer > div.row-form > span.block`
Privacy Policy `div.ml-form-embedContainer > div.row-form > span.block > a.underline`

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

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

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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

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

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

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	Map URL
mailerlite.com/tag/gtm.js?id=GTM-KKG2Q6R
assets.mailerlite.com/jsonp/2/forms?callback=ml.fn.renderPopupsAndPromotions
cdn.jsdelivr.net/npm/@growthbook/growthbook/dist/bundles/auto.min.js	cdn.jsdelivr.net/npm/@growthbook/growthbook/dist/bundles/auto.min.js.map

●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

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