Website review, no card needed

heveya.ae logo

heveya.ae website review

Visit site (opens in a new tab)Reviewed 16 November 202649 issues · 95 checks

This review found 49 issues worth fixing on heveya.ae, 15 of them high impact, across 95 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
4.9 s3.3 sMay 30Nov 144.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.5 s
Jun 6, 20263.6 s
Jun 13, 20263.8 s
Jun 20, 20264.0 s
Jun 27, 20264.0 s
Jul 4, 20264.2 s
Jul 11, 20264.1 s
Jul 18, 20263.9 s
Jul 25, 20264.0 s
Aug 1, 20264.0 s
Aug 8, 20264.0 s
Aug 15, 20264.1 s
Aug 22, 20264.1 s
Aug 29, 20264.3 s
Sep 5, 20264.4 s
Sep 12, 20264.5 s
Sep 19, 20264.5 s
Sep 26, 20264.5 s
Oct 3, 20264.7 s
Oct 10, 20264.7 s
Oct 17, 20264.7 s
Oct 24, 20264.5 s
Oct 31, 20264.3 s
Nov 7, 20264.3 s
Nov 14, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
511 ms332 msMay 30Nov 14464 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026353 ms
Jun 6, 2026354 ms
Jun 13, 2026356 ms
Jun 20, 2026357 ms
Jun 27, 2026367 ms
Jul 4, 2026367 ms
Jul 11, 2026375 ms
Jul 18, 2026375 ms
Jul 25, 2026378 ms
Aug 1, 2026378 ms
Aug 8, 2026375 ms
Aug 15, 2026381 ms
Aug 22, 2026396 ms
Aug 29, 2026423 ms
Sep 5, 2026439 ms
Sep 12, 2026446 ms
Sep 19, 2026464 ms
Sep 26, 2026468 ms
Oct 3, 2026476 ms
Oct 10, 2026490 ms
Oct 17, 2026444 ms
Oct 24, 2026444 ms
Oct 31, 2026441 ms
Nov 7, 2026457 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 heveya.ae (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. heveya.ae at 1.0 s1.0 s
  2. heveya.ae at 2.0 s2.0 s
  3. heveya.ae at 2.9 s2.9 s
  4. heveya.ae at 3.9 s3.9 s
  5. heveya.ae at 4.9 s4.9 s
  6. heveya.ae at 5.9 s5.9 s
  7. heveya.ae at 6.8 s6.8 s
  8. heveya.ae at 7.8 s7.8 s

Speed

12 to fix58
  • Render-blocking requests

    1.4 s

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

  • Main-thread work: 4.2 s

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

  • Mobile performance score: 58

    58/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Clarity and others), adding 1.3 MB and 840 ms of main-thread time.

  • Use efficient cache lifetimes

    650 ms · 250 KiB

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

  • Reduce unused JavaScript

    450 ms · 395 KiB

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

  • Improve image delivery

    500 ms · 277 KiB

    8 images could be 277 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 113 KiB

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

  • Google Tag Manager adds 264 ms

    264 ms

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

  • 2,445 HTML elements

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

  • Klaviyo adds 132 ms

    132 ms

    Klaviyo costs a phone 132 ms of main-thread work and 311 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.

  • Shopify adds 28 ms

    28 ms

    Shopify costs a phone 28 ms of main-thread work and 297 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.

  • Legacy JavaScript

    150 ms · 54 KiB

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

  • 10 long tasks on the main thread

    10 long tasks block the main thread while loading, the longest for 170 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: 14 ms

    14 ms

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

Core Web Vitals

11 to fix33
  • 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.2 s

    4.2 s

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

  • Real-user FCP: 3.5 s

    3.5 s

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

  • Largest Contentful Paint: 9.6 s

    9.6 s

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

  • Time to Interactive: 19.0 s

    19.0 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Real-user INP: 464 ms

    464 ms

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

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

    +30%

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Total Blocking Time: 254 ms

    254 ms

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

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

    +19%

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

2 checks passed
  • Real-user CLS: 0.05

    0.05

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

  • Cumulative Layout Shift: 0.038

    0.038

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

Images and page weight

2 to fix63
  • Page weight: 4.5 MB in 281 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 281 requests on a phone: images 1.6 MB (24), scripts 1.4 MB (82) and other files 1.1 MB (148). Under 2 MB keeps phones on slow connections fast.

  • 3 images below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.27 g

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

11 to fixGoogle 7486
  • 26 buttons without a name

    26 buttons have no accessible name, so screen readers announce just “button”.

  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

  • Elements must only use permitted ARIA attributes (18 elements)

    Elements must only use permitted ARIA attributes: 18 elements on the page fail this check, rated serious by axe-core.

  • 16 tap targets too small

    16 tap targets are too small or too close together to hit reliably with a finger.

  • 10 text elements with low contrast

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

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

  • Zoom is disabled

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

  • 11 links without text

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

  • 1 form field without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 80 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 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 11 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 8591
  • 5 H1 headlines

    There are 5 <h1> headlines (“Bringing Heveya's Sleep Expertise to the Maldives”, “Introducing the Heveya WOL Mattress” and “A New Standard for What You Sleep On”). One clear main headline is easier for people and search engines.

  • 12 links crawlers can't follow

    12 links have no real href, so search engines can't follow them.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 201 internal links, 12 external

    The homepage links to 201 pages on heveya.ae and 12 external pages.

7 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Heveya offers premium organic latex mattresses and natural bedding crafted for deep comfort. Visit our Al Quoz showroom…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Heveya Organic Latex Mattresses & Natural Bedding | Dubai”.

  • Canonical URL set

    The canonical URL is https://heveya.ae/.

  • Structured data in place

    Structured data found: Organization 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://heveya.ae/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://heveya.ae/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 (5,325 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 98 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    1 page 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 1 page 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 1 page that loaded have a <title>.

Best practices

5 to fixGoogle 5469
  • 7 broken images

    7 images failed to load on a phone, for example https://heveya.ae/.

  • 36 small tap targets

    36 of 72 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 1 third-party cookie

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

  • Browser-reported issues

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

1 checks passed
  • 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.

  • Thin social proof

    Social proof on the homepage: 16 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 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 1,562 words of copy

    The homepage carries about 1,562 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: “Shop Heveya® Mattresses Today” and “BOOK YOUR STAY”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Shop Heveya® Mattresses Today”, “Contact” and “Made to Order”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Opening hours shown

    Your opening hours are on the homepage.

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, Klaviyo 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.

  • 21 cookies set on arrival

    21

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

  • 42 other companies contacted

    Loading the homepage contacts 42 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 heveya.ae, 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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Judge Me Reviews · Promotion Popup Allnew · stamped.io · nfcube.com · weglot.com · snapchat.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 | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on heveya.ae, including 23 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