Website review, no card needed
idhlagency.com website review
Visit site (opens in a new tab)Reviewed 26 October 202618 issues · 77 checks
This review found 18 issues worth fixing on idhlagency.com, 5 of them high impact, across 77 checks. The most urgent: improve image delivery. 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
90AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.0 s |
| May 9, 2026 | 955 ms |
| May 16, 2026 | 979 ms |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 958 ms |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 981 ms |
| Jun 20, 2026 | 957 ms |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 104 ms |
| May 9, 2026 | 105 ms |
| May 16, 2026 | 105 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 110 ms |
| Jul 4, 2026 | 110 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 126 ms |
| Aug 1, 2026 | 136 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 135 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 123 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 127 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 123 ms |
| Oct 10, 2026 | 125 ms |
| Oct 17, 2026 | 125 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
Improve image delivery
1.2 s · 258 KiB5 images could be 258 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.4 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 80
80/100Your mobile performance score is 80 (desktop: 97). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 143 KiBAbout 143 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.
1,548 HTML elements
The page has 1,548 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 64 KiB6 files are served with short cache lifetimes, so returning visitors download them again (64 KiB).
1 third-party service on the page
1 third-party service load with your homepage (Optanon), adding 197 KiB and 91 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.
Reduce unused CSS
18 KiBAbout 18 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 148 ms of it running JavaScript. That is comfortably low.
Server response: 97 ms
97 msYour server sent the HTML in 97 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.7 s
4.7 sYour largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 104 ms to 125 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.0 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Time to Interactive: 4.7 s
4.7 sThe page becomes fully interactive after 4.7 s. Good is under 3.8 s.
9 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 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: 134 ms
134 msReal visitors wait 134 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.
Real-user TTFB: 720 ms
720 msReal visitors wait 720 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 2.9 s
2.9 sVisually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, 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
Page weight: 10.1 MB in 65 requests
10.1 MBYour homepage downloads 10.1 MB in 65 requests on a phone: media 9.3 MB (2), images 344 KiB (9) and scripts 232 KiB (6). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (62 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.9 g of CO₂ per visit
2.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.86 g of CO₂e: 343.0 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
24 text elements with low contrast
24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 53 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Integrated Digital Marketing Agency & Web Services | UK & USA | IDHL”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
66 internal links, 16 external
The homepage links to 66 pages on idhlagency.com and 16 external pages.
7 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “IDHL is a digital agency combining strategy, technology and marketing to help ambitious brands drive sustainable, long‑…”.
One H1 headline
Your main headline reads: “We are the leading performance marketing, web and commerce specialist. We combine experience, insight and AI innovation…”.
Canonical URL set
The canonical URL is https://www.idhlagency.com/.
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://www.idhlagency.com/sitemap.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (982 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.idhlagency.com/llms.txt (4 KiB, 23 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 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 15 pages that loaded have a <title>.
Best practices
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”.
2 checks passed
Tap targets are thumb-sized
30 of 30 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 950 words of copy
The homepage carries about 950 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: “GET IN TOUCH”.
5 calls to action
The homepage has 5 calls to action, for example “Get in touch”, “Talk to Us” and “Close Contact Form Modal”.
2 short forms
2 short forms (7 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks, 10 customer or partner logos and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 idhlagency.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- 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 18 issues on idhlagency.com, including 10 speed issues, 2 SEO issues and 1 conversion gap. 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.