Skip to content
https://whoispage.com

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.

75

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
whoispage.com/theme/default/fonts/fontawesome-webfont.woff?v=4.1.014400.0 s82.3 KiB
/theme/default/js/plugins/jvectormap/jquery-jvectormap-wo...14400.0 s49.9 KiB
whoispage.com/theme/default/img/img-icons-background.jpg14400.0 s33.5 KiB
/pagead/managed/js/adsense/m202607090101/show_ads_impl_fy...1209600.0 s165.8 KiB
whoispage.com/theme/default/css/theme.css14400.0 s23.5 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
whoispage.com/theme/default/img/no-preview.png14400.0 s12.9 KiB
whoispage.com/theme/default/js/AdminLTE/app.js14400.0 s12.8 KiB
whoispage.com/theme/default/css/AdminLTE.css14400.0 s12.4 KiB
whoispage.com/theme/default/js/plugins/morris/morris.min.js14400.0 s10.2 KiB
whoispage.com/theme/default/js/plugins/jvectormap/jquery-jvectormap-1.2.2.min.js14400.0 s9.2 KiB
whoispage.com/theme/default/js/bootstrap.min.js14400.0 s7.6 KiB
/beacon.min.js/v4513226cdae34746b4dedf0b4dfa099e178179150...86400.0 s11.3 KiB
whoispage.com/theme/default/css/ionicons.min.css14400.0 s6.1 KiB
whoispage.com/theme/default/js/plugins/jqueryKnob/jquery.knob.js14400.0 s5.9 KiB
whoispage.com/theme/default/css/font-awesome.min.css14400.0 s5.0 KiB
whoispage.com/core/img/logo.png14400.0 s3.6 KiB
whoispage.com/theme/default/css/reset.css14400.0 s2.8 KiB
whoispage.com/theme/default/img/twitter.png14400.0 s908 B
whoispage.com/theme/default/img/gp.png14400.0 s904 B
whoispage.com/theme/default/img/facebook.png14400.0 s721 B
whoispage.com/theme/default/css/jvectormap/jquery-jvectormap-1.2.2.css14400.0 s569 B
whoispage.com/theme/default/css/morris/morris.css14400.0 s545 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.

URLEst Savings
whoispage.com/theme/default/fonts/fontawesome-webfont.woff?v=4.1.0715 ms
/s/sourcesanspro/v23/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj...200 ms
/s/sourcesanspro/v23/6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdu...160 ms

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV
nodeLabel: WHOIS PAGE Quickly Calculate the Estimated Worth of Your Website and Build SEO …
path: 2,HTML,1,BODY,3,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,CENTER,0,DIV
selector: div#newcontent > div.wrapper > center > div.home
snippet: <div class="home">

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
/css?family=Source+Sans+Pro:300,400,600,300italic,400ital...1.1 KiB272 ms
fonts.googleapis.com/css?family=Kaushan+Script865 B
whoispage.com/theme/default/css/theme.css23.5 KiB300 ms
/css?family=Source+Sans+Pro:200,300,400,600,200italic,300...1.1 KiB1.2 s
whoispage.com/theme/default/css/font-awesome.min.css5.0 KiB
whoispage.com/theme/default/css/AdminLTE.css12.4 KiB
whoispage.com/theme/default/css/reset.css2.8 KiB150 ms
whoispage.com/theme/default/css/jvectormap/jquery-jvectormap-1.2.2.css569 B
whoispage.com/theme/default/css/morris/morris.css545 B
whoispage.com/theme/default/css/ionicons.min.css6.1 KiB

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
geiraonlus.it div.col-md-4 > div.thumbnail > a > img.image-overlay
whoispage.com/theme/default/img/no-preview.png12.4 KiB8.7 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

Diagnostics

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: 450 ms 33.8 KiB
URLTransfer SizeEst Savings
whoispage.com/theme/default/css/theme.css23.2 KiB21.9 KiB
whoispage.com/theme/default/css/AdminLTE.css12.1 KiB11.9 KiB

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 reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
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 CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.4 KiB
URLTransfer SizeEst Savings
whoispage.com/theme/default/css/AdminLTE.css12.4 KiB2.4 KiB

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 8.6 KiB
URLTransfer SizeEst Savings
whoispage.com/theme/default/js/AdminLTE/app.js12.3 KiB5.4 KiB
whoispage.com/theme/default/js/plugins/jqueryKnob/jquery.knob.js5.4 KiB3.1 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 177.4 KiB
URLTransfer SizeEst Savings
/pagead/managed/js/adsense/m202607090101/show_ads_impl_fy...165.7 KiB124.7 KiB
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js54.7 KiB29.3 KiB
cdnjs.cloudflare.com/ajax/libs/raphael/2.1.0/raphael-min.js26.8 KiB23.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
cnzz.com div.col-md-4 > div.thumbnail > a > img.image-overlay
whoispage.com/theme/default/img/no-preview.png
instagram.com div.col-md-4 > div.thumbnail > a > img.image-overlay
whoispage.com/theme/default/img/no-preview.png
mobilityweek.eu div.col-md-4 > div.thumbnail > a > img.image-overlay
whoispage.com/theme/default/img/no-preview.png
thecamdude.com div.col-md-4 > div.thumbnail > a > img.image-overlay
whoispage.com/theme/default/img/no-preview.png
soso.com div.col-md-4 > div.thumbnail > a > img.image-overlay
whoispage.com/theme/default/img/no-preview.png
geiraonlus.it div.col-md-4 > div.thumbnail > a > img.image-overlay
whoispage.com/theme/default/img/no-preview.png
worthmysite div.container > div.navbar-header > a.navbar-brand > img.worth_my_site_logo
whoispage.com/core/img/logo.png
google.com div.col-md-4 > div.thumbnail > a > img.image-overlay
whoispage.com/site_snapshot/google.com.jpg
instagram.com div.col-md-4 > div.thumbnail > a > img.image-overlay
whoispage.com/site_snapshot/instagram.com.jpg
twitter.com div.col-md-4 > div.thumbnail > a > img.image-overlay
whoispage.com/site_snapshot/twitter.com.jpg

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

●Max Potential First Input Delay 80 ms
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 697 KiB
●JavaScript execution time 0.5 s
●Minimizes main-thread work 1.5 s
●Avoid long main-thread tasks 5 long tasks found
●Avoid non-composited animations 1 animated element found
●Network Requests
●Network Round Trip Times 230 ms
●Server Backend Latencies 360 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 510 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
71

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.input-group > div.input-group-btn > button.btn div.row > div.input-group > div.input-group-btn > button.btn

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.container > div.row > div.none > a.ultm div.container > div.row > div.none > a.ultm
div.container > div.row > div.none > a.ultm div.container > div.row > div.none > a.ultm
div.container > div.row > div.none > a.ultm div.container > div.row > div.none > a.ultm

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.

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
Visit div.thumbnail > div.caption > p > a.btn
Details div.thumbnail > div.caption > p > a.btn
Visit div.thumbnail > div.caption > p > a.btn
Details div.thumbnail > div.caption > p > a.btn
Visit div.thumbnail > div.caption > p > a.btn
Details div.thumbnail > div.caption > p > a.btn
Visit div.thumbnail > div.caption > p > a.btn
Details div.thumbnail > div.caption > p > a.btn
Visit div.thumbnail > div.caption > p > a.btn
Details div.thumbnail > div.caption > p > a.btn
Visit div.thumbnail > div.caption > p > a.btn
Details div.thumbnail > div.caption > p > a.btn
Visit div.thumbnail > div.caption > p > a.btn
Details div.thumbnail > div.caption > p > a.btn
Visit div.thumbnail > div.caption > p > a.btn
Details div.thumbnail > div.caption > p > a.btn
Visit div.thumbnail > div.caption > p > a.btn
Details div.thumbnail > div.caption > p > a.btn

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
Quickly Calculate the Estimated Worth of Your Website and Build SEO reports as … div#myhome > div.container > div.row > h4
Google.com div.col-md-4 > div.thumbnail > div.caption > h4
Cnzz.com div.col-md-4 > div.thumbnail > div.caption > h4

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Identical links have the same purpose.
○`[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
○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 use only permitted 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
○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
○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 a valid value for its `[lang]` attribute
○`<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
○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 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>`.
○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

●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
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
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`

Send Feedback