Website review, no card needed

1hourdrain.com logo

1hourdrain.com website review

Visit site (opens in a new tab)Reviewed 8 November 202624 issues · 75 checks

This review found 24 issues worth fixing on 1hourdrain.com, 7 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of 1hourdrain.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1hourdrain.com at 0.4 s0.4 s
  2. 1hourdrain.com at 0.8 s0.8 s
  3. 1hourdrain.com at 1.1 s1.1 s
  4. 1hourdrain.com at 1.5 s1.5 s
  5. 1hourdrain.com at 1.9 s1.9 s
  6. 1hourdrain.com at 2.3 s2.3 s
  7. 1hourdrain.com at 2.6 s2.6 s
  8. 1hourdrain.com at 3.0 s3.0 s

Speed

4 to fix70
  • Render-blocking requests

    1.5 s

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

  • Improve image delivery

    1.1 s · 186 KiB

    3 images could be 186 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 70

    70/100

    Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    300 ms · 62 KiB

    About 62 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Font display

    50 ms

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (GoDaddy and secureserver.net), adding 31 KiB and 45 ms of main-thread time.

  • Reduce unused JavaScript

    40 KiB

    About 40 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    26 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (26 KiB).

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

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 215 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

3 to fix60
  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Cumulative Layout Shift: 0.214

    0.214

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

  • Time to Interactive: 5.3 s

    5.3 s

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

  • Not enough real-visitor data yet

    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.

3 checks passed
  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Speed Index: 1.5 s

    1.5 s

    Visually, the page fills in at 1.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix90
  • 1 image far larger than shown

    102 KiB

    1 image is downloaded at several times the size a phone draws it, for example Logo-White-1-768x367.png at 390 px wide, shown at 60 px. Resized copies would save about 102 KiB.

  • 3 images in older formats

    3 images (199 KiB) 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.

  • 1 image below the first screen load straight away

    1 image further down the page (34 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.3 g of CO₂ per visit

    0.26 g

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

1 checks passed
  • Page weight: 940 KiB in 62 requests

    940 KiB

    Your homepage downloads 940 KiB in 62 requests on a phone: fonts 313 KiB (7), images 299 KiB (5) and scripts 192 KiB (18). That is a lean page.

Accessibility

6 to fixGoogle 8791
  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • [role="img"] and [role="image"] elements must have alternative text (1 element)

    [role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (5 elements)

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (22 characters)

    Your title is only 22 characters: “1Hour Drain - San Jose”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 27 internal links, 12 external

    The homepage links to 27 pages on 1hourdrain.com and 12 external pages.

6 checks passed
  • Meta description: 123 characters

    Your meta description is 123 characters: “1Hour Drain - San Jose. The plumbing rooter specialist, Serving entire Bay Area. Contact us for quick quote & consultat…”.

  • Canonical URL set

    The canonical URL is https://1hourdrain.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://1hourdrain.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (452 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    / and https://1hourdrain.com/about-us all use the title “1Hour Drain - San Jose”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://1hourdrain.com/our-services, https://1hourdrain.com/faqs and https://1hourdrain.com/blog have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://1hourdrain.com/about-us and https://1hourdrain.com/contact-us use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://1hourdrain.com/about-us, https://1hourdrain.com/our-services, https://1hourdrain.com/contact-us, https://1hourdrain.com/faqs and https://1hourdrain.com/blog have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://1hourdrain.com/contact-us has 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.

  • 5 internal pages checked

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

4 checks passed
  • Linked pages load

    All 5 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Class extends value undefined is not a constructor or null”.

2 checks passed
  • Tap targets are thumb-sized

    13 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • 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: 15 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

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

  • No form on the homepage

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

  • No map or directions link

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

  • No risk reducer

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

  • About 432 words of copy

    The homepage carries about 432 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact us”, “CALL NOW” and “Contact Us”.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 4 cookies set on arrival

    4

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

  • No consent tool detected

    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.

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 1hourdrain.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
Cloudflare

Company

Headquarters
San Jose

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on 1hourdrain.com, including 7 speed issues, 2 SEO issues and 3 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