Website review, no card needed
hfsresearch.com website review
Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 82 checks
This review found 44 issues worth fixing on hfsresearch.com, 21 of them high impact, across 82 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
70C- #98,551 of 117,972 reviewed websitesbeats 14%
- #60,284 of 67,058 online storesbeats 8%
- #2,067 of 2,706 WooCommerce storesbeats 19%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 4.1 s |
| May 2, 2026 | 3.8 s |
| May 9, 2026 | 3.8 s |
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.2 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 4.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 129 ms |
| May 2, 2026 | 123 ms |
| May 9, 2026 | 121 ms |
| May 16, 2026 | 116 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 144 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 152 ms |
| Jul 4, 2026 | 135 ms |
| Jul 11, 2026 | 124 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 117 ms |
| Aug 1, 2026 | 109 ms |
| Aug 8, 2026 | 117 ms |
| Aug 15, 2026 | 114 ms |
| Aug 22, 2026 | 134 ms |
| Aug 29, 2026 | 134 ms |
| Sep 5, 2026 | 132 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 126 ms |
| Sep 26, 2026 | 125 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 121 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.9 s
1.7 s
2.6 s
3.5 s
4.3 s
5.2 s
6.0 s
6.9 s
Speed
Improve image delivery
68.4 s · 14.7 MB23 images could be 14.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 68.4 s faster on a phone.
Use efficient cache lifetimes
55.3 s · 12.3 MB174 files are served with short cache lifetimes, so returning visitors download them again (12.3 MB).
Reduce unused JavaScript
7.7 s · 1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.7 s faster on a phone.
Render-blocking requests
4.0 s50 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Reduce unused CSS
1.5 s · 205 KiBAbout 205 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Google CDN adds 1.1 s
1.1 sGoogle CDN costs a phone 1.1 s of main-thread work and 2.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 29
29/100Your mobile performance score is 29 (desktop: 31). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.1 s
A phone's processor spends 6.1 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 3.3 MB and 1.9 s of main-thread time.
Google Tag Manager adds 546 ms
546 msGoogle Tag Manager costs a phone 546 ms of main-thread work and 831 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 517 ms. During a long task the page ignores taps.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
Minify CSS
300 ms · 18 KiB18 KiB could be saved by minifying CSS.
1,648 HTML elements
The page has 1,648 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
8 KiB8 KiB could be saved by minifying JavaScript.
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: 6 ms
6 msYour server sent the HTML in 6 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 LCP: 4.5 s
4.5 sReal visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 14.1 s
14.1 sThe first text or image appears after 14.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 95.0 s
95.0 sYour largest element takes 95.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 32.5 s
32.5 sVisually, the page fills in at 32.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 95.7 s
95.7 sThe page becomes fully interactive after 95.7 s. Good is under 3.8 s.
Total Blocking Time: 801 ms
801 msScripts block taps and scrolling for 801 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.165
0.165The layout shifts by 0.165 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 129 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 4.1 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 21.7 MB in 236 requests
21.7 MBYour homepage downloads 21.7 MB in 236 requests on a phone: images 15.8 MB (70), scripts 4.3 MB (84) and other files 710 KiB (18). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 10.8 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
9.8 MB2 images are downloaded at several times the size a phone draws them, for example Vendor-Engagement-Program.png at 2,400 px wide, shown at 165 px. Resized copies would save about 9.8 MB.
8 images in older formats
8 images (11.8 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.
2 images below the first screen load straight away
2 images further down the page (5.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.1 g of CO₂ per visit
6.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.14 g of CO₂e: 736.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 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.
26 form fields without a label
26 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (8 elements)
Headings should not be empty: 8 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6, h3 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 28 images in the HTML carry an alt attribute.
44 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: 44 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
29 links crawlers can't follow
29 links have no real href, so search engines can't follow them.
Meta description is long (184 characters)
Your meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
200 internal links, 11 external
The homepage links to 200 pages on hfsresearch.com and 11 external pages.
7 checks passed
One H1 headline
Your main headline reads: “HFS RESEARCH”.
Title: 64 characters
Your title is a healthy 64 characters: “HFS Research | Technology, AI & Business Transformation Insights”.
Canonical URL set
The canonical URL is https://www.hfsresearch.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.hfsresearch.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.hfsresearch.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.
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: 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 (1,638 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 92 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
24 small tap targets
24 of 46 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 “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.5.0/css/all.css?ver=10aff6b31fdf793f5083c7b2d693c0…”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 16-field form
Your longest form asks for 16 fields (2 required). Every extra field lowers completion.
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,156 words of copy
The homepage carries about 1,156 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More” and “Subscribe”.
17 calls to action
The homepage has 17 calls to action, for example “Contact us”, “Register here” and “Register”.
Social proof on the page
Social proof on the homepage: 40 testimonial or review blocks and 3 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, HubSpot, LinkedIn Insight and Cloudflare Web Analytics.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
15 cookies set on arrival
15Opening the homepage sets 15 cookies (measured from a US location before any click).
26 other companies contacted
Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 hfsresearch.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
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- 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 44 issues on hfsresearch.com, including 25 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.