Website review, no card needed

havmor.com logo

havmor.com website review

Visit site (opens in a new tab)Reviewed 26 October 202649 issues · 88 checks

This review found 49 issues worth fixing on havmor.com, 24 of them high impact, across 88 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
3.7 s2.5 sMay 9Sep 263.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.1 s
May 16, 20263.0 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.8 s
Jun 13, 20262.9 s
Jun 20, 20262.8 s
Jun 27, 20262.6 s
Jul 18, 20263.5 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.6 s
Aug 15, 20263.5 s
Sep 19, 20262.7 s
Sep 26, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
246 ms109 msMay 9Sep 26153 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026136 ms
May 16, 2026134 ms
May 23, 2026132 ms
May 30, 2026132 ms
Jun 6, 2026128 ms
Jun 13, 2026125 ms
Jun 20, 2026125 ms
Jul 18, 2026226 ms
Jul 25, 2026226 ms
Aug 1, 2026228 ms
Aug 8, 2026230 ms
Aug 15, 2026220 ms
Sep 26, 2026153 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 havmor.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. havmor.com at 1.2 s1.2 s
  2. havmor.com at 2.5 s2.5 s
  3. havmor.com at 3.7 s3.7 s
  4. havmor.com at 4.9 s4.9 s
  5. havmor.com at 6.2 s6.2 s
  6. havmor.com at 7.4 s7.4 s
  7. havmor.com at 8.6 s8.6 s
  8. havmor.com at 9.9 s9.9 s

Speed

11 to fix26
  • Improve image delivery

    2.0 s · 10.6 MB

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

  • Render-blocking requests

    8.2 s

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

  • Reduce unused CSS

    5.1 s · 1,017 KiB

    About 1,017 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.1 s faster on a phone.

  • Minify CSS

    3.8 s · 728 KiB

    728 KiB could be saved by minifying CSS.

  • Reduce unused JavaScript

    2.1 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

  • Use efficient cache lifetimes

    1.6 s · 273 KiB

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

  • Mobile performance score: 26

    26/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and jQuery CDN and others), adding 1.4 MB and 1.0 s of main-thread time.

  • Google Tag Manager adds 581 ms

    581 ms

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

    400 ms · 37 KiB

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

  • Facebook adds 337 ms

    337 ms

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

  • Minify JavaScript

    238 KiB

    238 KiB could be saved by minifying JavaScript.

  • 13 long tasks on the main thread

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

  • Document request latency

    28 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

  • Server response: 463 ms

    463 ms

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

Core Web Vitals

8 to fix30
  • Largest Contentful Paint: 16.8 s

    16.8 s

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

  • Speed Index: 27.4 s

    27.4 s

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

  • Time to Interactive: 56.8 s

    56.8 s

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

  • First Contentful Paint: 7.4 s

    7.4 s

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

  • Cumulative Layout Shift: 0.434

    0.434

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

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

    +38%

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

  • 38 images without width and height

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

  • Total Blocking Time: 397 ms

    397 ms

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

4 to fix25
  • Page weight: 14.4 MB in 108 requests

    14.4 MB

    Your homepage downloads 14.4 MB in 108 requests on a phone: images 11.2 MB (45), scripts 2.0 MB (36) and stylesheets 1.1 MB (17). Under 2 MB keeps phones on slow connections fast.

  • 11 images over 500 KB

    11 images weigh 9.9 MB together. On a phone connection a single image that size takes seconds.

  • 16 images far larger than shown

    7.8 MB

    16 images are downloaded at several times the size a phone draws them, for example havmor-banner-gauva_0.jpg at 2,812 px wide, shown at 390 px. Resized copies would save about 7.8 MB.

  • 16 images in older formats

    16 images (11.0 MB) are 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.

  • 1 image below the first screen load straight away

    1 image further down the page (25 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 4.1 g of CO₂ per visit

    4.08 g

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

Accessibility

10 to fixGoogle 7786
  • Unlabelled dropdowns

    2 dropdowns have no label.

  • 30 text elements with low contrast

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

  • 3 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 9 images without alt text

    9 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (14 elements)

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

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

  • 36 links without text

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

  • 9 form fields without a label

    9 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

5 to fixGoogle 9271
  • No H1 headline

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

  • Title is short (8 characters)

    Your title is only 8 characters: “| Havmor”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (312 characters)

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

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

  • 51 internal links, 12 external

    The homepage links to 51 pages on havmor.com and 12 external pages.

3 checks passed
  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://havmor.com/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://havmor.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.

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 (398 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix88
  • 4 pages without a meta description

    https://havmor.com/lotte, https://havmor.com/Tub, https://havmor.com/Candy and https://havmor.com/chocolate have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://havmor.com/all-products, https://havmor.com/about-us, https://havmor.com/store-locator, https://havmor.com/leadership, https://havmor.com/contact-us and https://havmor.com/awards and 1 other use the same meta description. A description written for each page earns more clicks.

  • 8 pages without an H1

    https://havmor.com/all-products, https://havmor.com/about-us, https://havmor.com/leadership, https://havmor.com/lotte, https://havmor.com/Tub and https://havmor.com/Candy and 2 others 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 26 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

2 to fixGoogle 9687
  • 24 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Unexpected token '&'”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

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

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

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

    The homepage carries about 376 words of visible text.

4 checks passed
  • 1 short form

    A short form (7 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 5 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 4 cookies set on arrival

    4

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

  • 13 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery
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 49 issues on havmor.com, including 19 speed issues, 5 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