Skip to content
https://mez.ink

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.

69

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
mez.ink/mezink-web/fonts/InterVariable.woff214400.0 s344.5 KiB
mez.ink/mezink-web/home/features/feature-3.webp14400.0 s157.5 KiB
mez.ink/mezink-web/home/features/feature-1.webp14400.0 s28.2 KiB
mez.ink/mezink-web/home/extras/extras-1.webp14400.0 s24.8 KiB
mez.ink/mezink-web/home/global/map-mobile.webp14400.0 s21.0 KiB
mez.ink/mezink-web/home/features/feature-4.webp14400.0 s19.2 KiB
mez.ink/mezink-web/home/extras/extras-3.webp14400.0 s17.4 KiB
mez.ink/mezink-web/home/features/feature-5.webp14400.0 s14.8 KiB
mez.ink/mezink-web/home/features/feature-2.webp14400.0 s14.5 KiB
mez.ink/mezink-web/home/extras/extras-2.webp14400.0 s12.6 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
mez.ink/mezink-web/home/brands/brand-26.webp14400.0 s6.2 KiB
mez.ink/mezink-web/home/brands/brand-13.webp14400.0 s6.2 KiB
mez.ink/mezink-web/home/brands/brand-17.webp14400.0 s6.1 KiB
mez.ink/mezink-web/home/brands/brand-8.webp14400.0 s5.8 KiB
mez.ink/mezink-web/home/brands/brand-4.webp14400.0 s5.7 KiB
mez.ink/mezink-web/home/brands/brand-11.webp14400.0 s5.2 KiB
mez.ink/mezink-web/home/brands/brand-6.webp14400.0 s5.0 KiB
mez.ink/mezink-web/home/brands/brand-5.webp14400.0 s4.5 KiB
mez.ink/mezink-web/home/brands/brand-19.webp14400.0 s4.5 KiB
mez.ink/mezink-web/home/brands/brand-25.webp14400.0 s4.4 KiB
mez.ink/mezink-web/home/brands/brand-22.webp14400.0 s4.3 KiB
mez.ink/mezink-web/home/brands/brand-24.webp14400.0 s4.1 KiB
mez.ink/mezink-web/home/brands/brand-1.webp14400.0 s3.7 KiB
mez.ink/mezink-web/home/brands/brand-16.webp14400.0 s3.6 KiB
mez.ink/mezink-web/home/brands/brand-14.webp14400.0 s3.6 KiB
mez.ink/mezink-web/home/brands/brand-23.webp14400.0 s3.5 KiB
mez.ink/mezink-web/home/brands/brand-2.webp14400.0 s3.3 KiB
mez.ink/mezink-web/home/brands/brand-10.webp14400.0 s2.8 KiB
mez.ink/mezink-web/_static/mezink-logotype-light.svg14400.0 s2.8 KiB
mez.ink/mezink-web/_static/mezink-logotype-dark.svg14400.0 s2.8 KiB
mez.ink/mezink-web/home/brands/brand-3.webp14400.0 s2.7 KiB
mez.ink/mezink-web/home/brands/brand-18.webp14400.0 s2.6 KiB
mez.ink/mezink-web/home/brands/brand-21.webp14400.0 s2.6 KiB
mez.ink/mezink-web/home/brands/brand-7.webp14400.0 s2.4 KiB
mez.ink/mezink-web/home/brands/brand-12.webp14400.0 s2.2 KiB
mez.ink/mezink-web/home/brands/brand-20.webp14400.0 s2.1 KiB
mez.ink/mezink-web/home/brands/brand-9.webp14400.0 s2.1 KiB
mez.ink/mezink-web/home/brands/brand-15.webp14400.0 s2.0 KiB
mez.ink/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js2820.0 s809 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.

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:43.193 source:map[type:text value:[unattributed]]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1537.196 label:Time to first byte subpart:timeToFirstByte] map[duration:20.525 label:Resource load delay subpart:resourceLoadDelay] map[duration:1278.6 label:Resource load duration subpart:resourceLoadDuration] map[duration:79.09 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: Global presence map
path: 1,HTML,1,BODY,0,DIV,1,MAIN,2,DIV,0,DIV,0,DIV,1,DIV,0,PICTURE,2,IMG
selector: div.flex > div.juscetify-center > picture > img.h-[150px]
snippet: <img src="https://mez.ink/mezink-web/home/global/map-mobile.webp" alt="Global presence map" class="h-[150px] w-auto md:h-[294.86px] xl:h-[438px]" width="1100" height="438" loading="eager" fetchpriority="high">

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

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.

URLTransfer SizeDuration
mez.ink/mezink-web/_next/static/css/d77fb3338e59ac89.css773 B
mez.ink/mezink-web/_next/static/css/76d5f7d94bc07565.css31.5 KiB302 ms

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
Manage your entire program at scale div.mx-auto > div.relative > div.relative > img.h-full
mez.ink/mezink-web/home/features/feature-3.webp157.3 KiB108.8 KiB
Discover and recruit brand champions div.mx-auto > div.relative > div.relative > img.h-full
mez.ink/mezink-web/home/features/feature-1.webp28.1 KiB19.1 KiB
Partner with our expert strategists div.mx-auto > div.relative > div.relative > img.h-full
mez.ink/mezink-web/home/features/feature-4.webp19.1 KiB12.2 KiB
Access real-time data and ROI reporting div.mx-auto > div.relative > div.relative > img.h-full
mez.ink/mezink-web/home/features/feature-2.webp14.4 KiB9.3 KiB
Brand 25 div.group > div.flex > div.flex > img.h-full
mez.ink/mezink-web/home/brands/brand-26.webp6.1 KiB4.1 KiB
Brand 12 div.group > div.flex > div.flex > img.h-full
mez.ink/mezink-web/home/brands/brand-13.webp6.1 KiB4.1 KiB
Brand 16 div.group > div.flex > div.flex > img.h-full
mez.ink/mezink-web/home/brands/brand-17.webp5.9 KiB4.0 KiB

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.4 s
URLTime Spent
mez.ink/1.5 s

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: 350 ms 68.1 KiB
URLTransfer SizeEst Savings
mez.ink/mezink-web/_next/static/chunks/8382-9e4434d0c17bb1b2.js132.7 KiB68.1 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.

URLTotal CPU TimeScript EvaluationScript Parse
mez.ink/29.9 s79 ms26 ms
mez.ink/mezink-web/_next/static/chunks/2117-78579c6a0d6a0dcd.js2.6 s2.3 s17 ms
Unattributable2.0 s12 ms0.0 ms
mez.ink/mezink-web/_next/static/chunks/fd9d1056-70763ffa71ed5324.js850 ms238 ms20 ms
mez.ink/mezink-web/_next/static/chunks/8382-9e4434d0c17bb1b2.js759 ms182 ms50 ms
mez.ink/mezink-web/_next/static/chunks/webpack-ffb7e7628afde9c1.js220 ms214 ms1.4 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...181 ms107 ms4.3 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.

CategoryTime Spent
Other15.9 s
Rendering9.1 s
Style & Layout8.0 s
Script Evaluation3.2 s
Garbage Collection208 ms
Script Parsing & Compilation132 ms
Parse HTML & CSS128 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
storage.googleapis.com/super-content/images/upload/max-use-case_1749005464.png1.2 MiB
/super-content/images/upload/techmoint-case-study(1)_1748...1.0 MiB
storage.googleapis.com/super-content/images/upload/Porter-cover_1749003016.png706.0 KiB
api.cloudsuper.link/webpage/v1/case-study/list?page=1&limit=-1508.4 KiB
mez.ink/mezink-web/fonts/InterVariable.woff2344.5 KiB
storage.googleapis.com/super-content/images/upload/sharaf-dg(1)_1749004746.png317.6 KiB
mez.ink/mezink-web/home/features/feature-3.webp157.5 KiB
mez.ink/mezink-web/_next/static/chunks/8382-9e4434d0c17bb1b2.js132.8 KiB
mez.ink/mezink-web/_next/static/chunks/fd9d1056-70763ffa71ed5324.js52.7 KiB
mez.ink/mezink-web/_next/static/media/e4af272ccee01ff0-s.p.woff247.5 KiB

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

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoid long main-thread tasks 9 long tasks found
●Avoid non-composited animations 8 animated elements 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 1,730 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Avoid large layout shifts 15 layout shifts found
○INP breakdown
○User Timing marks and measures
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.

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
OUR GLOBAL PRESENCE div.flex > div.mx-auto > div.flex > p.text-primary
AI-POWERED DISCOVERY ENGINE div.grid > div.flex > div.flex > span.text-xs
AI-POWERED EVALUATION ENGINE div.grid > div.flex > div.flex > span.text-xs
AI CONTENT INTELLIGENCE div.grid > div.flex > div.flex > span.text-xs

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Strategic creator matching div.flex > div > div.mb-3 > h3.new-ui
Ideas to level-up your marketing game div.container > div.flex > div.flex > h3.text-base

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div.py-[64px] > div.mb-2.5 > div.flex > button.hover:bg-primary/20
Go to slide 2 div.py-[64px] > div.mb-2.5 > div.flex > button.hover:bg-primary/20
Go to slide 3 div.py-[64px] > div.mb-2.5 > div.flex > button.hover:bg-primary/20
Go to slide 4 div.py-[64px] > div.mb-2.5 > div.flex > button.hover:bg-primary/20
Go to slide 2 main > div.py-16 > div.mt-6 > button.hover:bg-primary/20
Go to slide 3 main > div.py-16 > div.mt-6 > button.hover:bg-primary/20
Go to slide 4 main > div.py-16 > div.mt-6 > button.hover:bg-primary/20
Go to slide 5 main > div.py-16 > div.mt-6 > button.hover:bg-primary/20
Go to slide 6 main > div.py-16 > div.mt-6 > button.hover:bg-primary/20

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
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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 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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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
○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.
100

Best Practices

●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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
91

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
mez.ink/industry/tiktok-shop-brandsLearn more
mez.ink/marketing-leaders/jason-barnardRead More
mez.ink/marketing-leaders/christian-brownRead More
mez.ink/marketing-leaders/jessica-sandersonRead More
mez.ink/marketing-leaders/shane-hodgeRead More
mez.ink/marketing-leaders/vedrac-rasicRead More
mez.ink/marketing-leaders/anton-shulkeRead 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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○robots.txt is valid
○Document has a valid `rel=canonical`

Send Feedback