Programmable

Website review, no card needed

plumberslu130ua.com logo

plumberslu130ua.com website review

Visit site (opens in a new tab)Reviewed 20 October 202637 issues · 83 checks

This review found 37 issues worth fixing on plumberslu130ua.com, 12 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

70C

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.1 s834 msMay 2Oct 17979 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.2 s
May 9, 20261.2 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.1 s
Jun 27, 20261.2 s
Jul 4, 20261.7 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.7 s
Aug 1, 20261.2 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 2026989 ms
Oct 10, 2026990 ms
Oct 17, 2026979 ms
Real-visitor tap response (INP)75th percentile, phones
87 ms77 msMay 2Oct 1780 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202684 ms
May 9, 202684 ms
May 16, 202681 ms
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202678 ms
Jun 20, 202678 ms
Jun 27, 202680 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202679 ms
Jul 25, 202680 ms
Aug 1, 202679 ms
Aug 8, 202682 ms
Aug 15, 202682 ms
Aug 22, 202680 ms
Aug 29, 202680 ms
Sep 5, 202685 ms
Sep 12, 202685 ms
Sep 19, 202686 ms
Sep 26, 202684 ms
Oct 3, 202679 ms
Oct 10, 202680 ms
Oct 17, 202680 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

plumberslu130ua.com (opens in a new tab)
Full-page screenshot of plumberslu130ua.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. plumberslu130ua.com at 0.7 s0.7 s
  2. plumberslu130ua.com at 1.4 s1.4 s
  3. plumberslu130ua.com at 2.1 s2.1 s
  4. plumberslu130ua.com at 2.8 s2.8 s
  5. plumberslu130ua.com at 3.5 s3.5 s
  6. plumberslu130ua.com at 4.2 s4.2 s
  7. plumberslu130ua.com at 4.9 s4.9 s
  8. plumberslu130ua.com at 5.6 s5.6 s

Speed

11 to fix37

  • Use efficient cache lifetimes

    9.1 s · 8.6 MB

    58 files are served with short cache lifetimes, so returning visitors download them again (8.6 MB).

  • Render-blocking requests

    6.5 s

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

  • Reduce unused CSS

    4.5 s · 891 KiB

    About 891 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.5 s faster on a phone.

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37 (desktop: 83). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    900 ms · 5.9 MB

    21 images could be 5.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • Reduce unused JavaScript

    450 ms · 497 KiB

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

  • Minify CSS

    750 ms · 134 KiB

    134 KiB could be saved by minifying CSS.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Fonts and others), adding 618 KiB and 606 ms of main-thread time.

  • Google Tag Manager adds 604 ms

    604 ms

    Google Tag Manager costs a phone 604 ms of main-thread work and 479 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 3.4 s

    A phone's processor spends 3.4 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 long tasks on the main thread

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

  • Font display

    250 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

  • Minify JavaScript

    47 KiB

    47 KiB could be saved by minifying JavaScript.

  • Document request latency

    42 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    37 KiB

    Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 83 but mobile only 37. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed

  • Server response: 89 ms

    89 ms

    Your server sent the HTML in 89 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100

  • Largest Contentful Paint: 11.3 s

    11.3 s

    Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome to Local 130 Plumbers / Technical Engineers / Journ…”.

  • First Contentful Paint: 7.2 s

    7.2 s

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

  • Speed Index: 12.6 s

    12.6 s

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

  • Time to Interactive: 15.4 s

    15.4 s

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

  • Total Blocking Time: 445 ms

    445 ms

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

  • Cumulative Layout Shift: 0.164

    0.164

    The layout shifts by 0.164 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 14 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 84 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 checks passed

  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.9 s

    1.9 s

    Real visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 617 ms

    617 ms

    Real visitors wait 617 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 18% faster for real visitors

    -18%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

1 to fix0

  • Page weight: 9.3 MB in 78 requests

    9.3 MB

    Your homepage downloads 9.3 MB in 78 requests on a phone: images 7.0 MB (34), scripts 1.1 MB (18) and stylesheets 940 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • About 2.6 g of CO₂ per visit

    2.63 g

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

Accessibility

5 to fix68

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 7 links without text

    7 links have no text or label, so screen readers cannot say where they go.

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • No main landmark

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed

  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

SEO

6 to fixGoogle 9282

  • Canonical points to another host

    Your canonical URL points to plumbers130ua.org, not plumberslu130ua.com, so Google may credit that host instead.

  • No structured data

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

  • No social preview image

    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

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

  • No favicon declared

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

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

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

  • 64 internal links, 20 external

    The homepage links to 64 pages on plumberslu130ua.com and 20 external pages.

4 checks passed

  • Meta description: 149 characters

    Your meta description is 149 characters: “Official site of the Chicago Journeymen Plumbers - the only plumbers union approved within the City of Chicago and the …”.

  • One H1 headline

    Your main headline reads: “Local 130 Proudly Supports Attorney General Raoul's Lawsuit Against ABC Plumbing, Heating, Cooling & Electric for Unfai…”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Homepage | Plumbers Local 130 UA”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83

  • No Organization structured data

    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.

  • No llms.txt

    There is no https://plumberslu130ua.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.

1 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

2 to fix80

  • 3 pages without a title

    https://plumberslu130ua.com/history.aspx, https://plumberslu130ua.com/technical-engineers.aspx and https://plumberslu130ua.com/territorial.aspx have no <title>, so Google invents the link text in results.

  • 11 pages without a meta description

    https://plumberslu130ua.com/about.aspx, https://plumberslu130ua.com/events.aspx, https://plumberslu130ua.com/officers.aspx, https://plumberslu130ua.com/history.aspx, https://plumberslu130ua.com/plumbers.aspx and https://plumberslu130ua.com/technical-engineers.aspx and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages with very little text

    https://plumberslu130ua.com/about.aspx, https://plumberslu130ua.com/history.aspx, https://plumberslu130ua.com/technical-engineers.aspx and https://plumberslu130ua.com/territorial.aspx have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.

5 checks passed

  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 7388

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 8 distorted images

    8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88

  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: “over 6,100 members”. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

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

  • About 731 words of copy

    The homepage carries about 731 words of visible text.

6 checks passed

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at plumberslu130ua.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on plumberslu130ua.com, including 18 speed issues, 6 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25