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
a4.pbase.com/g9/17/104817/3/164329103.H5qfpVZD.jpg	0.0 ms	30.6 KiB
a4.pbase.com/g1/89/259589/3/112396030.z3bcxwYj.jpg	0.0 ms	25.6 KiB
a4.pbase.com/o4/87/331787/1/61501002.leica_r8_LR02999028420.jpg	0.0 ms	15.1 KiB
a4.pbase.com/u38/world_images/upload/24960600.smlgflag.gif	0.0 ms	5.2 KiB
ap1.pbase.com/js/common.js	0.0 ms	3.7 KiB
ap1.pbase.com/site/rc/dark_gray_5_top.png	0.0 ms	3.2 KiB
ap1.pbase.com/site/rc/light_gray_5_top.png	0.0 ms	3.2 KiB
ap1.pbase.com/site/rc/dark_gray_5_bot.png	0.0 ms	3.2 KiB
ap1.pbase.com/site/rc/light_gray_5_bot.png	0.0 ms	3.2 KiB
ap1.pbase.com/styles/common.css	0.0 ms	1.9 KiB
ap1.pbase.com/styles/main.css	0.0 ms	933 B
ap1.pbase.com/site/pb_logo.gif	0.0 ms	611 B
ap1.pbase.com/site/tabs/1r.gif	0.0 ms	603 B
ap1.pbase.com/site/search.gif	0.0 ms	581 B
ap1.pbase.com/js/main.js	0.0 ms	501 B
ap1.pbase.com/site/tabs/1l.gif	0.0 ms	416 B

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

nodeLabel: Featured Gallery

path: 1,HTML,1,BODY,2,DIV,0,DIV,2,DIV,0,DIV,2,DIV,0,A,0,IMG

selector: div.c > div#featured_gallery > a.thumbnail > img.thumbnail

snippet: <img class="thumbnail" src="https://a4.pbase.com/g13/61/1159561/2/176172703.c29af3a4.JPEG" width="400" height="300" border="0" alt="Featured Gallery" loading="lazy">

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

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
ap1.pbase.com/js/main.js	501 B
ap1.pbase.com/styles/common.css	1.9 KiB	757 ms
ap1.pbase.com/js/common.js	3.7 KiB
ap1.pbase.com/styles/main.css	933 B	150 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.

	URL	Resource Size	Est Savings
Featured Gallery `div.c > div#featured_gallery > a.thumbnail > img.thumbnail`	a4.pbase.com/g13/61/1159561/2/176172703.c29af3a4.JPEG	98.7 KiB	38.9 KiB
Countries `tr > td > a.thumbnail > img.thumbnail`	a4.pbase.com/g9/17/104817/3/164329103.H5qfpVZD.jpg	30.2 KiB	24.2 KiB
Topic `tr > td > a.thumbnail > img.thumbnail`	a4.pbase.com/g1/89/259589/3/112396030.z3bcxwYj.jpg	25.2 KiB	16.6 KiB
Flag `td > p > a.thumbnail > img.thumbnail`	a4.pbase.com/u38/world_images/upload/24960600.smlgflag.gif	4.8 KiB	4.7 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.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Time to Interactive 1.8 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 200 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.4 s

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

○INP breakdown

○User Timing marks and measures

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

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
Host and share your photos on the Internet. `body > div#header > h3`
Topics `tbody > tr > th > 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.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
search pbase.com `div#header > form#search > div > input`

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
Topics `tr > th > h4 > a`
San Marino `tr > td > p > 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>`

●Image elements have `[alt]` attributes

●`<input type="image">` elements have `[alt]` text

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Identical links have the same purpose.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

○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

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

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

○No element has a `[tabindex]` value greater than 0

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

○Elements with visible text labels have matching accessible names.

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

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
1	`<html lang="en-US"><head>`	`Syntax not understood`
2	`<title>pbase Artist romee</title>`	`Syntax not understood`
3	`<link rel="stylesheet" type="text/css" href="https://ap1.pbase.com/styles/gallery2.v4.css">`	`Unknown directive`
4	`<link rel="stylesheet" type="text/css" href="https://ap1.pbase.com/styles/comments.v2.css">`	`Unknown directive`
5	`<link rel="stylesheet" type="text/css" href="https://ap1.pbase.com/styles/gallery2.v4.css">`	`Unknown directive`
6	`<link rel="alternate" href="https://feeds.pbase.com/feeds/robots/galleries.atom" title="romee's Gallery Updates" type="application/atom+xml" />`	`Unknown directive`
7	`</head><body>`	`Syntax not understood`
8	`<TABLE border=0 cellspacing=0 cellpadding=0 width="100%"><tr>`	`Syntax not understood`
9	`<td><A HREF="https://pbase.com" target="_top" title="pbase photos"><IMG src="https://ap1.pbase.com/site/m_pbase.gif" border=0 alt="photo sharing and upload"></A></td>`	`Unknown directive`
10	`<td><A HREF="https://pbase.com/galleries" target="_top" title="recent picture uploads"><IMG src="https://ap1.pbase.com/site/m_g.gif" border=0 alt="picture albums"></A></td>`	`Unknown directive`
11	`<td><A HREF="https://forum.pbase.com" target="_top" title="photography discussion forums"><IMG src="https://ap1.pbase.com/site/m_f.gif" border=0 alt="photo forums"></A></td>`	`Unknown directive`
12	`<td><A HREF="https://pbase.com/search" target="_top" title="pbase photo search"><IMG src="https://ap1.pbase.com/site/m_s.gif" border=0 alt="search pictures"></A></td>`	`Unknown directive`
13	`<td width="100%"><A HREF="https://pbase.com/galleries?view=popular" target="_top" title="popular photos"><IMG src="https://ap1.pbase.com/site/m_sp.gif" border=0 height="28" width="100%" alt="popular photos"></a></td>`	`Unknown directive`
15	`<td><A HREF="https://pbase.com/help" target="_top" title="give me some help"><IMG src="https://ap1.pbase.com/site/m_h.gif" border=0 alt="photography help"></A></td>`	`Unknown directive`
16	`<td><A HREF="https://pbase.com/login" target="_top" title="login to pbase"><IMG src="https://ap1.pbase.com/site/m_l.gif" border=0 alt="login"></A></td>`	`Unknown directive`
17	`</tr></table>`	`Syntax not understood`
18	`<!-- END menu bar -->`	`Syntax not understood`
20	`<table border=0 width="100%">`	`Syntax not understood`
21	`<tr>`	`Syntax not understood`
22	`<td align=left >`	`Syntax not understood`
23	`<b>`	`Syntax not understood`
24	`romee`	`Syntax not understood`
25	`\|`	`Syntax not understood`
26	`profile`	`Syntax not understood`
27	`\|`	`Syntax not understood`
28	`<a HREF="/robots/guestbook" title="goto robots's guestbook">guestbook</a>`	`Syntax not understood`
29	`\|`	`Syntax not understood`
30	`<a href="/robots" title="goto robots's galleries">all galleries</a>`	`Syntax not understood`
31	`\|`	`Syntax not understood`
32	`<a href="/robots/root&view=recent" title="robots's recent galleries" rel="nofollow">recent</a>`	`Syntax not understood`
33	`</b>`	`Syntax not understood`
34	`</td>`	`Syntax not understood`
35	`</tr>`	`Syntax not understood`
36	`</table>`	`Syntax not understood`
37	`<br>`	`Syntax not understood`
39	`<!-- begin box -->`	`Syntax not understood`
40	`<TABLE cellSpacing=0 cellPadding=1 border=0 width="98%" align="center">`	`Syntax not understood`
41	`<TBODY>`	`Syntax not understood`
42	`<TR><TD class="ma">Profile for romee`	`Syntax not understood`
43	`<TABLE cellSpacing=0 cellPadding=2 width="100%" border=0 bgcolor="#ffffff">`	`Syntax not understood`
44	`<TBODY>`	`Syntax not understood`
45	`<tr><td class="wb">`	`Syntax not understood`
47	`<TABLE border=0 width="100%">`	`Syntax not understood`
48	`<tr><td valign="top">`	`Syntax not understood`
50	`<TABLE border=0>`	`Syntax not understood`
51	`<tr>`	`Syntax not understood`
52	`<td class=mi>Name</td>`	`Syntax not understood`
53	`<td class=wb>romee <span class="small">(joined 11-Mar-2026)`	`Syntax not understood`
54	`</span>`	`Syntax not understood`
55	`</td>`	`Syntax not understood`
56	`</tr>`	`Syntax not understood`
58	`<tr>`	`Syntax not understood`
59	`<td class=mi>Username</td>`	`Syntax not understood`
60	`<td class=wb>robots</td>`	`Syntax not understood`
61	`</tr>`	`Syntax not understood`
63	`<tr>`	`Syntax not understood`
64	`<td class=mi>Location</td>`	`Syntax not understood`
65	`<td class=wb>United States</td>`	`Syntax not understood`
66	`</tr>`	`Syntax not understood`
67	`</table>`	`Syntax not understood`
68	`</td>`	`Syntax not understood`
69	`<td align=right valign=top class=wb>`	`Syntax not understood`
70	`<a href="/world/united_states" alt="united_states">`	`Syntax not understood`
71	`<IMG class=thumbnail src="https://a4.pbase.com/u38/world_images/100/24960632.uslgflag.jpg" WIDTH=100 HEIGHT=53 border=2 alt="united_states" loading="lazy" >`	`Unknown directive`
72	`</a>`	`Syntax not understood`
73	`<br>`	`Syntax not understood`
74	`United States`	`Syntax not understood`
75	`</td>`	`Syntax not understood`
76	`</tr>`	`Syntax not understood`
77	`</table>`	`Syntax not understood`
79	`</td></tr>`	`Syntax not understood`
80	`</TBODY>`	`Syntax not understood`
81	`</TABLE>`	`Syntax not understood`
82	`</TD></TR>`	`Syntax not understood`
84	`</TBODY>`	`Syntax not understood`
85	`</TABLE>`	`Syntax not understood`
86	`<!-- end box-->`	`Syntax not understood`
88	`<!-- begin box -->`	`Syntax not understood`
89	`<TABLE cellSpacing=0 cellPadding=1 border=0 width="98%" align="center">`	`Syntax not understood`
90	`<TBODY>`	`Syntax not understood`
91	`<TR><TD class="mi">Statistics`	`Syntax not understood`
92	`<TABLE cellSpacing=0 cellPadding=2 width="100%" border=0 bgcolor="#ffffff">`	`Syntax not understood`
93	`<TBODY>`	`Syntax not understood`
94	`<tr><td class="wb">`	`Syntax not understood`
96	`romee has no images online.<br>These pages have been viewed a total of <b>0</b> times.`	`Syntax not understood`
97	`<br>`	`Syntax not understood`
98	`<br>`	`Syntax not understood`
99	`<a href="/robots/guestbook">View Guestbook</a> :`	`Unknown directive`
100	`No guestbook messages.`	`Syntax not understood`
101	`<br><br>`	`Syntax not understood`
102	`</td></tr>`	`Syntax not understood`
103	`</TBODY>`	`Syntax not understood`
104	`</TABLE>`	`Syntax not understood`
105	`</TD></TR>`	`Syntax not understood`
107	`</TBODY>`	`Syntax not understood`
108	`</TABLE>`	`Syntax not understood`
109	`<!-- end box-->`	`Syntax not understood`
110	`<br>`	`Syntax not understood`
112	`</body>`	`Syntax not understood`
113	`</html>`	`Syntax not understood`

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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`