Website review, no card needed

whitehorse.my logo

whitehorse.my website review

Visit site (opens in a new tab)Reviewed 23 October 202636 issues · 78 checks

This review found 36 issues worth fixing on whitehorse.my, 14 of them high impact, across 78 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

Real-visitor load time (LCP)75th percentile, phones
3.3 s1.5 sMay 2Oct 173.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.1 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20261.9 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20262.0 s
Jul 11, 20262.1 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.4 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.3 s
Sep 26, 20262.5 s
Oct 3, 20262.8 s
Oct 10, 20263.0 s
Oct 17, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
107 ms73 msMay 2Oct 17102 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202684 ms
May 9, 202685 ms
May 16, 202685 ms
May 23, 202689 ms
May 30, 202689 ms
Jun 6, 202688 ms
Jun 13, 202685 ms
Jun 20, 202678 ms
Jun 27, 202677 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202683 ms
Jul 25, 202684 ms
Aug 1, 202686 ms
Aug 8, 202684 ms
Aug 15, 202686 ms
Aug 22, 202684 ms
Aug 29, 202683 ms
Sep 5, 202688 ms
Sep 12, 202689 ms
Sep 19, 202697 ms
Sep 26, 2026100 ms
Oct 3, 2026100 ms
Oct 10, 2026103 ms
Oct 17, 2026102 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 whitehorse.my (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. whitehorse.my at 2.0 s2.0 s
  2. whitehorse.my at 3.9 s3.9 s
  3. whitehorse.my at 5.9 s5.9 s
  4. whitehorse.my at 7.9 s7.9 s
  5. whitehorse.my at 9.8 s9.8 s
  6. whitehorse.my at 11.8 s11.8 s
  7. whitehorse.my at 13.8 s13.8 s
  8. whitehorse.my at 15.8 s15.8 s

Speed

8 to fix59
  • Render-blocking requests

    1.6 s

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

  • Font display

    1.1 s

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

  • Use efficient cache lifetimes

    900 ms · 3.1 MB

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

  • Mobile performance score: 59

    59/100

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

  • Improve image delivery

    780 KiB

    10 images could be 780 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    600 ms · 146 KiB

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

  • Google Tag Manager adds 402 ms

    402 ms

    Google Tag Manager costs a phone 402 ms of main-thread work and 318 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: 2.6 s

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 319 KiB and 402 ms of main-thread time.

  • Reduce unused CSS

    290 ms · 32 KiB

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

  • 5 long tasks on the main thread

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

  • 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: 455 ms

    455 ms

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

Core Web Vitals

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

  • Real-user LCP: 4.1 s

    4.1 s

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • Speed Index: 18.4 s

    18.4 s

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

  • Largest Contentful Paint: 8.1 s

    8.1 s

    Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (8.1 s).

  • Time to Interactive: 8.3 s

    8.3 s

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

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

    +21%

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

  • Largest content (LCP) got 58% slower for real visitors

    +58%

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

  • 24 images without width and height

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

  • Total Blocking Time: 291 ms

    291 ms

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

4 checks passed
  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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.

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

1 to fix70
  • Page weight: 8.1 MB in 92 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 92 requests on a phone: media 4.8 MB (1), images 2.7 MB (21) and scripts 529 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

    2 images further down the page (45 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.3 g of CO₂ per visit

    2.31 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8592
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 13 text elements with low contrast

    13 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 (26 elements)

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

  • No main landmark

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

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

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

  • 195 internal links, 9 external

    The homepage links to 195 pages on whitehorse.my and 9 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Ultimate Quality, Timeless Design”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “White Horse | White Horse Ceramic”.

  • Canonical URL set

    The canonical URL is https://whitehorse.my/.

  • 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://whitehorse.my/wp-sitemap.xml.

AI search readiness

1 to fix88
  • 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://whitehorse.my/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.

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://whitehorse.my/products, https://whitehorse.my/product-category/glazed-polished, https://whitehorse.my/product-category/ceramic-floor-wall, https://whitehorse.my/product-category/ceramic-wall-tiles, https://whitehorse.my/product-category/porcelain and https://whitehorse.my/product-category/polished-porcelain and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://whitehorse.my/product-category/glazed-polished, https://whitehorse.my/product-category/ceramic-floor-wall, https://whitehorse.my/product-category/ceramic-wall-tiles, https://whitehorse.my/product-category/porcelain, https://whitehorse.my/product-category/polished-porcelain and https://whitehorse.my/product-category/decor 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 33 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10092
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix63
  • 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.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 300 words of visible text.

2 checks passed
  • 3 calls to action

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 9 cookies set on arrival

    9

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 whitehorse.my, 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
E-commerce
WooCommerce
Analytics
Google 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 36 issues on whitehorse.my, including 19 speed issues, 3 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