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

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

value: No additional origins are good candidates for preconnecting

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
s.plurk.com/621a5cbd66c1ad116e38.js	25.6 KiB	616 ms
s.plurk.com/f7479daa39fc09939d33.js	27.0 KiB	616 ms
s.plurk.com/9a5fab0f605e484dd773.js	1.8 KiB	166 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/4.2.0/css/font-awesome.min.css	4.6 KiB	917 ms
s.plurk.com/0b4c6bba169d05713bfa.css	1.3 KiB	766 ms
s.plurk.com/6e5cf14de24bfbb2867d.css	9.1 KiB	1.1 s
cdnjs.cloudflare.com/ajax/libs/sweetalert/2.1.2/sweetalert.min.js	0 B	464 ms
s.plurk.com/d32550ffee1f96e9b7be.js	0 B	466 ms
cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js	0 B
s.plurk.com/df8ad868ef05e65d0132.js	0 B	166 ms
cdnjs.cloudflare.com/ajax/libs/handlebars.js/1.3.0/handlebars.min.js	0 B	464 ms
s.plurk.com/1caeb4b31b8ba4ddf68a.css	0 B	766 ms
s.plurk.com/dbd9daa27a81c57db4df.css	0 B	766 ms
s.plurk.com/723a4498be4c0f0df690.js	0 B	166 ms
s.plurk.com/7f1add5e26234962cdbf.js	0 B	166 ms

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
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	0 B

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
s.plurk.com/plurkiconfont/fonts/c0679c24afdce236d7fa.woff2	15 ms

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: 6.6 s

URL	Time Spent
plurk.com/	775 ms
www.plurk.com/	780 ms
www.plurk.com/m/	5.0 s
www.plurk.com/login?r=https%3A%2F%2Fwww.plurk.com%2Fm%2F	0.0 ms

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.

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

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: 3.2 s 883.6 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	143.1 KiB
s.plurk.com/eb28ab34edc2862d3ed4.js	98.7 KiB	79.1 KiB
s.plurk.com/7f1add5e26234962cdbf.js	70.8 KiB	67.0 KiB
s.plurk.com/7f1add5e26234962cdbf.js	70.8 KiB	65.5 KiB
www.googletagmanager.com/gtag/js?id=G-15X0DLSVWS	160.1 KiB	62.8 KiB
www.googletagmanager.com/gtag/js?id=G-15X0DLSVWS	160.1 KiB	61.9 KiB
s.plurk.com/d32550ffee1f96e9b7be.js	48.4 KiB	47.6 KiB
s.plurk.com/d32550ffee1f96e9b7be.js	48.4 KiB	47.6 KiB
s.plurk.com/d32550ffee1f96e9b7be.js	48.4 KiB	47.6 KiB
s.plurk.com/723a4498be4c0f0df690.js	45.0 KiB	44.0 KiB
s.plurk.com/723a4498be4c0f0df690.js	45.0 KiB	44.0 KiB
s.plurk.com/723a4498be4c0f0df690.js	45.0 KiB	43.4 KiB
s.plurk.com/f46e679bbbd66dee3363.js	66.0 KiB	34.0 KiB
s.plurk.com/d32550ffee1f96e9b7be.js	48.4 KiB	30.2 KiB
s.plurk.com/723a4498be4c0f0df690.js	45.0 KiB	23.0 KiB
s.plurk.com/f7479daa39fc09939d33.js	26.5 KiB	22.0 KiB
s.plurk.com/d32550ffee1f96e9b7be.js	48.4 KiB	21.0 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
www.googletagmanager.com/gtag/js?id=G-15X0DLSVWS	1.2 s	864 ms	285 ms
s.plurk.com/eb28ab34edc2862d3ed4.js	1.0 s	868 ms	59 ms
Unattributable	452 ms	19 ms	0.0 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	368 ms	271 ms	92 ms
cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js	248 ms	187 ms	49 ms
www.plurk.com/login?r=https%3A%2F%2Fwww.plurk.com%2Fm%2F	225 ms	14 ms	5.7 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	201 ms	66 ms	15 ms
s.plurk.com/d32550ffee1f96e9b7be.js	153 ms	18 ms	132 ms
s.plurk.com/7f1add5e26234962cdbf.js	138 ms	8.4 ms	129 ms
s.plurk.com/723a4498be4c0f0df690.js	138 ms	16 ms	120 ms
s.plurk.com/f7479daa39fc09939d33.js	137 ms	122 ms	15 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	123 ms	103 ms	18 ms
s.plurk.com/df8ad868ef05e65d0132.js	87 ms	84 ms	3.1 ms
cdnjs.cloudflare.com/ajax/libs/sweetalert/2.1.2/sweetalert.min.js	82 ms	55 ms	25 ms
s.plurk.com/621a5cbd66c1ad116e38.js	54 ms	44 ms	9.9 ms
cdnjs.cloudflare.com/ajax/libs/handlebars.js/1.3.0/handlebars.min.js	54 ms	30 ms	23 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.8 s
Script Parsing & Compilation	1.0 s
Other	543 ms
Style & Layout	232 ms
Parse HTML & CSS	95 ms
Garbage Collection	58 ms
Rendering	9.6 ms

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

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 959 KiB

●User Timing marks and measures 14 user timings

●Avoid long main-thread tasks 19 long tasks 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 20 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○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
Register `div#top-bar-user > ul.item-container > li#navbar-register > a#bar-register`
Forgot your password? `div.login-holder > form#login_form > div#reset_password > a`
Login `div.content-holder > div.login-holder > form#login_form > button#login_submit`
Your login will be remembered for 14 days (or until logout). `div.login-holder > form#login_form > div#term > p`
© 2008-2026 Plurk `footer.clearfix > div#footer > ul > li.copyright`
2026 Plurk `div#footer > ul > li.copyright > span#footer-year`
Plurk `ul > li.copyright > span#footer-year > span`
About `div#footer > ul > li > a`
Brand Assets `div#footer > ul > li > a`
Verified Account `div#footer > ul > li > a`
Terms `div#footer > ul > li > a`
Privacy `div#footer > ul > li > a`
Content Policy `div#footer > ul > li > a`
FAQ `div#footer > ul > li > a`
Contact Us `div#footer > ul > li > a`

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English 中文 (繁體) 中文 (香港) 中文 (简体) 日本語 Filipino Bahasa Indonesia Bahasa Melayu Pус… `div#languge_selector > i > form > select`

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#top-bar-main > ul.item-container > li#navbar-portal > a `div#top-bar-main > ul.item-container > li#navbar-portal > 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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
Brand Assets `div#footer > ul > li > a`
Verified Account `div#footer > ul > li > a`
Terms `div#footer > ul > li > a`
Content Policy `div#footer > ul > li > a`
FAQ `div#footer > ul > li > a`
Contact Us `div#footer > ul > li > a`

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

●Buttons have an accessible name

●Form elements have associated labels

●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

●The page contains a heading, skip link, or landmark region

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

○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

○Elements use only permitted ARIA attributes

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

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

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

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

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○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

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

○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

●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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`