pplumbing.com website review

5 images could be 4.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 20.7 s faster on a phone.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

Your mobile performance score is 56 (desktop: 66). Pages that score under 90 lose visitors before the first paint.

About 109 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 610 ms faster on a phone.

4 long tasks block the main thread while loading, the longest for 234 ms. During a long task the page ignores taps.

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 226 KiB and 135 ms of main-thread time.

1 file is served with short cache lifetimes, so returning visitors download them again (11 KiB).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 37.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “PPI crew on a service call”.

Visually, the page fills in at 17.5 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 38.8 s. Good is under 3.8 s.

The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 263 ms in total while the page loads. Good is under 200 ms.

1 image have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 8.7 MB in 22 requests on a phone: images 8.4 MB (13), scripts 302 KiB (3) and fonts 48 KiB (1). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example crew-service-portrait.jpg at 4,284 px wide, shown at 356 px. Resized copies would save about 6.9 MB.

5 images weigh 5.7 MB together. On a phone connection a single image that size takes seconds.

13 images (8.4 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

11 images further down the page (7.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 2.47 g of CO₂e: 296.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

Google's crawler is blocked from indexing this page.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://pplumbing.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at pplumbing.com/robots.txt, the first file search crawlers ask for.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 29 pages on pplumbing.com and 1 external page.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://pplumbing.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://pplumbing.com/services, https://pplumbing.com/about, https://pplumbing.com/careers, https://pplumbing.com/request-service, https://pplumbing.com/contact and https://pplumbing.com/service-area are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://pplumbing.com/services and https://pplumbing.com/service-area use the same meta description. A description written for each page earns more clicks.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 828 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 2 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.