Website review, no card needed
hamelinbrands.com website review
Visit site (opens in a new tab)Reviewed 19 November 202618 issues · 70 checks
This review found 18 issues worth fixing on hamelinbrands.com, 8 of them high impact, across 70 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.5 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 77 ms |
| Jun 6, 2026 | 77 ms |
| Jun 13, 2026 | 70 ms |
| Jun 20, 2026 | 70 ms |
| Jun 27, 2026 | 71 ms |
| Jul 4, 2026 | 74 ms |
| Jul 11, 2026 | 76 ms |
| Jul 18, 2026 | 78 ms |
| Jul 25, 2026 | 78 ms |
| Aug 1, 2026 | 74 ms |
| Aug 8, 2026 | 72 ms |
| Aug 15, 2026 | 72 ms |
| Aug 22, 2026 | 75 ms |
| Aug 29, 2026 | 78 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 77 ms |
| Sep 19, 2026 | 73 ms |
| Sep 26, 2026 | 73 ms |
| Oct 3, 2026 | 74 ms |
| Oct 10, 2026 | 75 ms |
| Oct 17, 2026 | 78 ms |
| Oct 24, 2026 | 76 ms |
| Oct 31, 2026 | 72 ms |
| Nov 7, 2026 | 71 ms |
| Nov 14, 2026 | 71 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.8 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Reduce unused JavaScript
300 ms · 63 KiBAbout 63 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
250 ms · 71 KiB6 files are served with short cache lifetimes, so returning visitors download them again (71 KiB).
Reduce unused CSS
150 ms · 49 KiBAbout 49 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (kiprotect.com, cleantalk.org and Adobe TypeKit), adding 76 KiB and 43 ms of main-thread time.
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.
3 checks passed
Mobile performance score: 98
98/100Your mobile performance score is 98. That is in Google's “good” band (90 and up).
Main-thread work: 0.2 s
A phone's processor spends 0.2 s on main-thread work while loading, 78 ms of it running JavaScript. That is comfortably low.
Server response: 64 ms
64 msYour server sent the HTML in 64 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 TTFB: 939 ms
939 msReal visitors wait 939 ms for your server to start answering (75th percentile). Good is under 800 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 77 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 58 ms
58 msReal visitors wait 58 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.2 s
2.2 sYour largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “We use cookies to provide you with the best browsing experi…”.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Speed Index: 2.4 s
2.4 sVisually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.
Time to Interactive: 2.2 s
2.2 sThe page is fully interactive after 2.2 s.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.07 g of CO₂ per visit
0.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.07 g of CO₂e: 8.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 260 KiB in 24 requests
260 KiBYour homepage downloads 260 KiB in 24 requests on a phone: scripts 139 KiB (8), stylesheets 54 KiB (5) and fonts 43 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 1 internal link
The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.
6 checks passed
One H1 headline
Your main headline reads: “You are currently visiting Hamelin Brands Global (English)”.
Title: 38 characters
Your title is a healthy 38 characters: “Home Global - Hamelin Brands Corporate”.
Canonical URL set
The canonical URL is https://www.hamelinbrands.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage 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://www.hamelinbrands.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.hamelinbrands.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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Other pages
1 internal page checked
We fetched 1 page linked from your homepage and read each the way a search engine does.
7 checks passed
Linked pages load
All 1 page we checked loaded without an error.
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
15 small tap targets
15 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
Only about 67 words
The homepage has only about 67 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
17 cookies set on arrival
17Opening the homepage sets 17 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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 hamelinbrands.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on hamelinbrands.com, including 5 speed issues, 3 SEO issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.