Website review, no card needed

emperormarble.co.uk logo

emperormarble.co.uk website review

Visit site (opens in a new tab)Reviewed 10 November 202619 issues · 72 checks

This review found 19 issues worth fixing on emperormarble.co.uk, 7 of them high impact, across 72 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
2.5 s712 msMay 23Nov 71.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.0 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20261.9 s
Jul 25, 20261.6 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20261.8 s
Sep 5, 20261.4 s
Sep 12, 2026996 ms
Sep 19, 2026923 ms
Sep 26, 20261.0 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.2 s
Oct 24, 20261.0 s
Nov 7, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
107 ms78 msMay 23Nov 796 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202697 ms
May 30, 2026104 ms
Jun 6, 2026100 ms
Jun 13, 202695 ms
Jun 20, 2026101 ms
Jun 27, 202698 ms
Jul 4, 202693 ms
Jul 11, 202688 ms
Jul 18, 202681 ms
Jul 25, 202688 ms
Aug 1, 202693 ms
Aug 8, 202695 ms
Aug 15, 2026100 ms
Aug 22, 202696 ms
Aug 29, 202695 ms
Sep 5, 202694 ms
Sep 12, 202699 ms
Oct 24, 202685 ms
Nov 7, 202696 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 emperormarble.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. emperormarble.co.uk at 0.5 s0.5 s
  2. emperormarble.co.uk at 1.1 s1.1 s
  3. emperormarble.co.uk at 1.6 s1.6 s
  4. emperormarble.co.uk at 2.2 s2.2 s
  5. emperormarble.co.uk at 2.7 s2.7 s
  6. emperormarble.co.uk at 3.2 s3.2 s
  7. emperormarble.co.uk at 3.8 s3.8 s
  8. emperormarble.co.uk at 4.3 s4.3 s

Speed

4 to fix71
  • Improve image delivery

    7.1 s · 1.7 MB

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

  • Mobile performance score: 71

    71/100

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

  • Render-blocking requests

    800 ms

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

  • Use efficient cache lifetimes

    650 ms · 105 KiB

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

  • Reduce unused JavaScript

    190 ms · 48 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Hubspot, Shopify and revenuehunt.com and others), adding 177 KiB and 161 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 14 KiB

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

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    15 KiB

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

  • 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: 2.0 s

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

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 17.6 s

    17.6 s

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

  • Time to Interactive: 18.0 s

    18.0 s

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

  • Speed Index: 5.0 s

    5.0 s

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

8 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 CLS: 0.00

    0.00

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

  • Real-user FCP: 0.7 s

    0.7 s

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

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

    -10%

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

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

    -54%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.0 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.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 31 ms

    31 ms

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

Images and page weight

2 to fix64
  • Page weight: 4.0 MB in 177 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 177 requests on a phone: images 2.7 MB (38), other files 623 KiB (60) and scripts 463 KiB (55). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    render-collection-matrix-01.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.1 g of CO₂ per visit

    1.14 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 137.3 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

5 to fixGoogle 9394
  • 3 text elements with low contrast

    3 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 (3 elements)

    All page content should be contained by landmarks: 3 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.

  • 10 links without text

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

    Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 40 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 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 10092
  • Meta description is long (166 characters)

    Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 112 internal links, 5 external

    The homepage links to 112 pages on emperormarble.co.uk and 5 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Wholesale marble, onyx and natural stone slabs for bulk and project buyers.”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Wholesale Marble & Natural Stone Slabs, London | Emperor Marble”.

  • Canonical URL set

    The canonical URL is https://emperormarble.co.uk/.

  • 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://emperormarble.co.uk/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://emperormarble.co.uk/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: 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 (1,086 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 2 pages that loaded have a meta description.

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

  • Every page has a title

    All 2 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    46 of 49 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 792 words of visible text.

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact”, “Talk to the team” and “Contact the team”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 5 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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 emperormarble.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Simprosys Google Shopping Feed · revenuehunt.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on emperormarble.co.uk, including 7 speed issues, 2 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