Skip to content
https://page.tl

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
app.varify.io/varify.js120.0 s21.1 KiB
cdn.matomo.cloud/webme.matomo.cloud/container_nrGM1OYG.js691200.0 s54.0 KiB

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.

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
wtheme.webme.com/js/jquery-3.7.1.min.jshttp/1.1
wtheme.webme.com/js/jquery-migrate-3.5.2.min.jshttp/1.1
wtheme.webme.com/js/main73.jshttp/1.1
wtheme.webme.com/css/bootstrap.min.csshttp/1.1
wtheme.webme.com/css/bootstrap-responsive.min.csshttp/1.1
wtheme.webme.com/css/style23.csshttp/1.1
wtheme.webme.com/img/main/en/logo.pnghttp/1.1
wtheme.webme.com/img/main/by-Webme.svghttp/1.1
wtheme.webme.com/img/main/placeholder.pnghttp/1.1
wtheme.webme.com/js/bootstrap.min.jshttp/1.1
wtheme.webme.com/js/bootstrap-slider.jshttp/1.1
wtheme.webme.com/img/main/arrow.pnghttp/1.1
wtheme.webme.com/img/main/en/example1.jpghttp/1.1
wtheme.webme.com/img/main/en/example2.jpghttp/1.1
wtheme.webme.com/img/main/en/example3.jpghttp/1.1
wtheme.webme.com/img/main/pig.jpghttp/1.1
wtheme.webme.com/img/main/thumb.jpghttp/1.1
wtheme.webme.com/img/main/seo.jpghttp/1.1
wtheme.webme.com/img/main/designs.jpghttp/1.1
wtheme.webme.com/img/main/favicon.icohttp/1.1

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
wtheme.webme.com/js/main73.js21.9 KiB1.5 s
wtheme.webme.com/css/bootstrap.min.css21.7 KiB1.5 s
wtheme.webme.com/js/jquery-3.7.1.min.js35.0 KiB1.7 s
wtheme.webme.com/css/style23.css9.3 KiB1.2 s
wtheme.webme.com/js/jquery-migrate-3.5.2.min.js5.8 KiB1.0 s
wtheme.webme.com/css/bootstrap-responsive.min.css4.2 KiB836 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
https://penta-network.page.tl/ ul.thumbnails > li > a.thumbnail > img.js
wtheme.webme.com/img/main/en/example1.jpg20.5 KiB12.3 KiB
https://greenwoodgarden.page.tl/ ul.thumbnails > li > a.thumbnail > img.js
wtheme.webme.com/img/main/en/example3.jpg16.6 KiB8.4 KiB
https://barreramusic.page.tl/ ul.thumbnails > li > a.thumbnail > img.js
wtheme.webme.com/img/main/en/example2.jpg16.3 KiB8.2 KiB

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 863 ms
URLTime Spent
page.tl/863 ms
www.own-free-website.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

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: 150 ms 19.5 KiB
URLTransfer SizeEst Savings
wtheme.webme.com/css/bootstrap.min.css21.3 KiB19.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
by Webme div.pull-left > div.pull-left > a > img
wtheme.webme.com/img/main/by-Webme.svg

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
●Forced reflow
●LCP breakdown
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 651 KiB
●JavaScript execution time 0.1 s
●Minimizes main-thread work 0.3 s
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 70 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 40 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
92

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

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.js > iframe#banner body.js > iframe#banner

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

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
Private div.span200px > ul.unstyled > li > a
Starter div.span200px > ul.unstyled > li > a
Board div.span200px > ul.unstyled > li > a
Support div.span200px > ul.unstyled > li > a
Protection of Minors div.span200px > ul.unstyled > li > a
Investigative Authorities div.span200px > ul.unstyled > li > a

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Do not use optional cookies body.js > div#cookieConsent > div#cookieConsentDiv > a#cookieConsentDismiss
Use optional cookies body.js > div#cookieConsent > div#cookieConsentDiv > a#cookieConsentAllow
○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
●Image elements have `[alt]` attributes
●`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.
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`[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 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
○Buttons have an accessible name
○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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
92

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
https://penta-network.page.tl/ ul.thumbnails > li > a.thumbnail > img.js
wtheme.webme.com/img/main/en/example1.jpg260 x 193 (1.35)290 x 200 (1.45)
https://barreramusic.page.tl/ ul.thumbnails > li > a.thumbnail > img.js
wtheme.webme.com/img/main/en/example2.jpg260 x 193 (1.35)290 x 200 (1.45)
https://greenwoodgarden.page.tl/ ul.thumbnails > li > a.thumbnail > img.js
wtheme.webme.com/img/main/en/example3.jpg260 x 193 (1.35)290 x 200 (1.45)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
https://penta-network.page.tl/ ul.thumbnails > li > a.thumbnail > img.js
wtheme.webme.com/img/main/en/example1.jpg260 x 193290 x 200390 x 290
https://barreramusic.page.tl/ ul.thumbnails > li > a.thumbnail > img.js
wtheme.webme.com/img/main/en/example2.jpg260 x 193290 x 200390 x 290
https://greenwoodgarden.page.tl/ ul.thumbnails > li > a.thumbnail > img.js
wtheme.webme.com/img/main/en/example3.jpg260 x 193290 x 200390 x 290
Own-Free-Website.com - Create your own free Website! div > div.pull-left > a.pull-left > img#logo
wtheme.webme.com/img/main/en/logo.png367 x 55367 x 55551 x 83
100% for free! li > div.thumbnail > div.imageContainer > img.js
wtheme.webme.com/img/main/pig.jpg125 x 128125 x 128188 x 192
Without any coding skills! li > div.thumbnail > div.imageContainer > img.js
wtheme.webme.com/img/main/thumb.jpg70 x 13070 x 130105 x 195
●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
●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
92

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

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Yes body.js > div#topContainer > div#unsavedChanges > a.btn
No body.js > div#topContainer > div#unsavedChanges > a.btn

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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback