Website review, no card needed

homzmart.com logo

homzmart.com website review

Visit site (opens in a new tab)Reviewed 17 November 202646 issues · 89 checks

This review found 46 issues worth fixing on homzmart.com, 20 of them high impact, across 89 checks. The most urgent: improve image delivery. 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
6.1 s3.8 sMay 30Nov 144.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.0 s
Jun 6, 20265.0 s
Jun 13, 20265.0 s
Jun 20, 20265.0 s
Jun 27, 20265.2 s
Jul 4, 20265.4 s
Jul 11, 20265.5 s
Jul 18, 20265.8 s
Jul 25, 20265.8 s
Aug 1, 20265.7 s
Aug 8, 20265.8 s
Aug 15, 20265.7 s
Aug 22, 20265.7 s
Aug 29, 20265.9 s
Sep 5, 20265.6 s
Sep 12, 20265.2 s
Sep 19, 20264.9 s
Sep 26, 20264.5 s
Oct 3, 20264.3 s
Oct 10, 20264.2 s
Oct 17, 20264.2 s
Oct 24, 20264.1 s
Oct 31, 20264.1 s
Nov 7, 20264.1 s
Nov 14, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
511 ms328 msMay 30Nov 14464 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026374 ms
Jun 6, 2026364 ms
Jun 13, 2026349 ms
Jun 20, 2026350 ms
Jun 27, 2026358 ms
Jul 4, 2026380 ms
Jul 11, 2026402 ms
Jul 18, 2026427 ms
Jul 25, 2026422 ms
Aug 1, 2026413 ms
Aug 8, 2026430 ms
Aug 15, 2026423 ms
Aug 22, 2026448 ms
Aug 29, 2026486 ms
Sep 5, 2026484 ms
Sep 12, 2026490 ms
Sep 19, 2026486 ms
Sep 26, 2026472 ms
Oct 3, 2026475 ms
Oct 10, 2026474 ms
Oct 17, 2026470 ms
Oct 24, 2026471 ms
Oct 31, 2026464 ms
Nov 7, 2026469 ms
Nov 14, 2026464 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 homzmart.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. homzmart.com at 1.4 s1.4 s
  2. homzmart.com at 2.9 s2.9 s
  3. homzmart.com at 4.3 s4.3 s
  4. homzmart.com at 5.7 s5.7 s
  5. homzmart.com at 7.2 s7.2 s
  6. homzmart.com at 8.6 s8.6 s
  7. homzmart.com at 10.0 s10.0 s
  8. homzmart.com at 11.5 s11.5 s

Speed

12 to fix24
  • Improve image delivery

    1.5 s · 30.0 MB

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

  • Main-thread work: 10.6 s

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

  • Mobile performance score: 24

    24/100

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

  • 5,745 HTML elements

    The page has 5,745 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Use efficient cache lifetimes

    150 ms · 31.5 MB

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

  • Reduce unused JavaScript

    900 ms · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.7 MB and 1.1 s of main-thread time.

  • 11 long tasks on the main thread

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

  • Google Tag Manager adds 584 ms

    584 ms

    Google Tag Manager costs a phone 584 ms of main-thread work and 684 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

    650 ms

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

  • Google Maps adds 73 ms

    73 ms

    Google Maps costs a phone 73 ms of main-thread work and 333 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.

  • Server response: 600 ms

    600 ms

    Your server takes 600 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Minify JavaScript

    150 ms · 11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    69 KiB

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

  • Reduce unused CSS

    22 KiB

    About 22 KiB of CSS is downloaded but never applied on this page.

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

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

Core Web Vitals

12 to fix0
  • 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.

  • Real-user LCP: 4.9 s

    4.9 s

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

  • Real-user CLS: 0.59

    0.59

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

  • Real-user FCP: 4.2 s

    4.2 s

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

  • Real-user TTFB: 3.4 s

    3.4 s

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

  • Largest Contentful Paint: 11.1 s

    11.1 s

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

  • Speed Index: 17.2 s

    17.2 s

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

  • Time to Interactive: 27.6 s

    27.6 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.393

    0.393

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

  • Real-user INP: 481 ms

    481 ms

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

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

    +26%

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

2 checks passed
  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

1 to fix70
  • Page weight: 35.7 MB in 353 requests

    35.7 MB

    Your homepage downloads 35.7 MB in 353 requests on a phone: images 31.5 MB (152), scripts 2.8 MB (78) and fonts 1.0 MB (12). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (316 KiB) is 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.

  • About 10.1 g of CO₂ per visit

    10.12 g

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

2 checks passed
  • 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

7 to fixGoogle 8590
  • 23 text elements with low contrast

    23 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 (10 elements)

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

  • Zoom is disabled

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

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

  • 30 links without text

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

  • Alternative text of images should not be repeated as text (22 elements)

    Alternative text of images should not be repeated as text: 22 elements on the page fail this check, rated minor 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 634 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

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

SEO

3 to fixGoogle 10080
  • No H1 headline

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

  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “هومزمارت أكبر موقع للأثاث المنزلي , اشتري أون لاين بأفضل سعر فى مصر”.

  • 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 X (Twitter) card tag

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

  • 155 internal links, 2 external

    The homepage links to 155 pages on homzmart.com and 2 external pages.

5 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “تسوق الآن كل ما يحتاجه بيتك من الأثاث المنزلي والديكور والأثاث المكتبى والأجهزة المنزلية من موقع هومزمارت. اشتري بأفضل …”.

  • Canonical URL set

    The canonical URL is https://homzmart.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
  • No llms.txt

    There is no https://homzmart.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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix75
  • 10 pages without a title

    https://homzmart.com/furniture, https://homzmart.com/appliances, https://homzmart.com/lifestyle, https://homzmart.com/kids, https://homzmart.com/campaign/Novemberdeals and https://homzmart.com/showroom-locations and 4 others have no <title>, so Google invents the link text in results.

  • 10 pages without a meta description

    https://homzmart.com/furniture, https://homzmart.com/appliances, https://homzmart.com/lifestyle, https://homzmart.com/kids, https://homzmart.com/campaign/Novemberdeals and https://homzmart.com/showroom-locations and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://homzmart.com/en, https://homzmart.com/furniture, https://homzmart.com/appliances, https://homzmart.com/lifestyle, https://homzmart.com/kids and https://homzmart.com/campaign/Novemberdeals and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages with very little text

    https://homzmart.com/furniture, https://homzmart.com/appliances, https://homzmart.com/lifestyle, https://homzmart.com/kids, https://homzmart.com/campaign/Novemberdeals and https://homzmart.com/showroom-locations and 7 others 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.

  • 5 pages slow to respond

    https://homzmart.com/en, https://homzmart.com/c/furniture, https://homzmart.com/c/mkt/deal-of-the-day, https://homzmart.com/p/mdf-wardrobe-2-doors-220x120x50-cm--BA3CON1759 and https://homzmart.com/p/mdf-wooden-bedroom-set-4-pieces--ARTOFURNCON551827 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 6988
  • 1 third-party cookie

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.

  • 10 distorted images

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

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    68 of 82 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 196 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 form on the homepage

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

  • 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 574 words of copy

    The homepage carries about 574 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (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.

  • 28 other companies contacted

    Loading the homepage contacts 28 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 homzmart.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
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on homzmart.com, including 24 speed issues, 3 SEO 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