Website review, no card needed

homejoy.com logo

homejoy.com website review

Visit site (opens in a new tab)Reviewed 6 November 202630 issues · 81 checks

This review found 30 issues worth fixing on homejoy.com, 10 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
3.3 s2.6 sMay 16Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.0 s
May 23, 20263.1 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20262.9 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Oct 31, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
199 ms174 msMay 16Oct 31195 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026177 ms
May 23, 2026179 ms
May 30, 2026183 ms
Jun 6, 2026184 ms
Jun 13, 2026186 ms
Jun 20, 2026187 ms
Jun 27, 2026191 ms
Jul 4, 2026194 ms
Jul 11, 2026194 ms
Jul 18, 2026194 ms
Jul 25, 2026192 ms
Aug 1, 2026192 ms
Aug 8, 2026193 ms
Aug 15, 2026194 ms
Aug 22, 2026194 ms
Aug 29, 2026193 ms
Sep 5, 2026192 ms
Sep 12, 2026190 ms
Sep 19, 2026191 ms
Sep 26, 2026192 ms
Oct 3, 2026193 ms
Oct 10, 2026193 ms
Oct 17, 2026194 ms
Oct 24, 2026196 ms
Oct 31, 2026195 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

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

How it loaded on a phone

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

Speed

8 to fix37
  • Reduce unused JavaScript

    1.7 s · 646 KiB

    About 646 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.

  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 6.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, TikTok and Snapchat and others), adding 667 KiB and 981 ms of main-thread time.

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    467 KiB

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

  • Facebook adds 394 ms

    394 ms

    Facebook costs a phone 394 ms of main-thread work and 270 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.

  • Render-blocking requests

    350 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

  • Legacy JavaScript

    150 ms · 55 KiB

    Polyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    150 ms · 19 KiB

    1 image could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Forced reflow

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Total Blocking Time: 2.7 s

    2.7 s

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

  • Time to Interactive: 17.6 s

    17.6 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Real-user INP: 203 ms

    203 ms

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

  • Real-user TTFB: 914 ms

    914 ms

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

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

    1.6 s

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

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

    -13%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 121 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 121 requests on a phone: scripts 1.8 MB (44), images 125 KiB (20) and other files 48 KiB (49). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.59 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9796
  • 5 text elements with low contrast

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

Google 100100
  • Open Graph partly set

    Open Graph is missing og:title, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 36 internal links, 17 external

    The homepage links to 36 pages on homejoy.com and 17 external pages.

7 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Find top rated house cleaners near you. Professional, affordable and background-checked. Get your first 3-hour clean fr…”.

  • One H1 headline

    Your main headline reads: “Get your first home cleaning free! | Homeaglow Introductory Deal”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Homeaglow – Official Site | Get Your First House Cleaning Free”.

  • Canonical URL set

    The canonical URL is https://www.homeaglow.com/.

  • Structured data in place

    Structured data found: FAQPage and Organization.

  • 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://www.homeaglow.com/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.homeaglow.com/llms.txt (4 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://www.homeaglow.com/apply declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 4 pages share 2 titles

    https://www.homeaglow.com/help and https://www.homeaglow.com/help/ticket all use the title “Customer Service & Help Center”, and 1 other title repeat too. 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://www.homeaglow.com/help, https://www.homeaglow.com/redeem and https://www.homeaglow.com/help/ticket have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.homeaglow.com/redeem and https://www.homeaglow.com/customer/choosedate have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7797
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    5 of 6 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix78
  • 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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 1,014 words of copy

    The homepage carries about 1,014 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get your free cleaning”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Get your free cleaning” and “Contact us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: a star rating and “served 200,000+ customers”.

  • Risk reducer mentioned

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Microsoft Ads and Pinterest Tag and 2 mores (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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 17 other companies contacted

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

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 homejoy.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
Next.js
Hosting
Enflow B.V.

Company

Founded
2012
Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on homejoy.com, including 16 speed issues and 4 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