Website review, no card needed
hmmglobal.com website review
Visit site (opens in a new tab)Reviewed 22 October 202646 issues · 81 checks
This review found 46 issues worth fixing on hmmglobal.com, 19 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
65DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
20.1 s · 5.2 MBAbout 5.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 20.1 s faster on a phone.
Render-blocking requests
5.2 s65 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.2 s.
Reduce unused CSS
2.7 s · 536 KiBAbout 536 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.7 s faster on a phone.
webee.io adds 1.8 s
1.8 swebee.io costs a phone 1.8 s of main-thread work and 8.4 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: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 3.2 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 (webee.io, Google Tag Manager and Google CDN and others), adding 10.4 MB and 2.7 s of main-thread time.
Use efficient cache lifetimes
700 ms · 560 KiB17 files are served with short cache lifetimes, so returning visitors download them again (560 KiB).
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 781 ms. During a long task the page ignores taps.
Google Tag Manager adds 311 ms
311 msGoogle Tag Manager costs a phone 311 ms of main-thread work and 508 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.
Google CDN adds 277 ms
277 msGoogle CDN costs a phone 277 ms of main-thread work and 734 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.
Google Maps adds 103 ms
103 msGoogle Maps costs a phone 103 ms of main-thread work and 383 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 · 26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
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
First Contentful Paint: 16.2 s
16.2 sThe first text or image appears after 16.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 71.5 s
71.5 sYour largest element takes 71.5 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: 35.9 s
35.9 sVisually, the page fills in at 35.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 91.7 s
91.7 sThe page becomes fully interactive after 91.7 s. Good is under 3.8 s.
Total Blocking Time: 751 ms
751 msScripts block taps and scrolling for 751 ms in total while the page loads. Good is under 200 ms.
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.
1 checks passed
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 22.2 MB in 269 requests
22.2 MBYour homepage downloads 22.2 MB in 269 requests on a phone: scripts 10.2 MB (93), images 7.8 MB (38) and media 2.2 MB (2). Under 2 MB keeps phones on slow connections fast.
8 images over 500 KB
8 images weigh 4.6 MB together. On a phone connection a single image that size takes seconds.
8 images far larger than shown
2.3 MB8 images are downloaded at several times the size a phone draws them, for example slider_mobile_hmm-05-scaled.png at 1,999 px wide, shown at 310 px. Resized copies would save about 2.3 MB.
20 images in older formats
20 images (7.2 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.
14 images below the first screen load straight away
14 images further down the page (3.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.3 g of CO₂ per visit
6.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.28 g of CO₂e: 753.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
10 buttons without a name
10 buttons have no accessible name, so screen readers announce just “button”.
33 text elements with low contrast
33 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 (9 elements)
All page content should be contained by landmarks: 9 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.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 38 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 4 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 H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (10 characters)
Your title is only 10 characters: “HMM Global”. 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.
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.
10 links crawlers can't follow
10 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
53 internal links, 6 external
The homepage links to 53 pages on hmmglobal.com and 6 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://hmmglobal.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://hmmglobal.com/sitemap.xml.
AI search readiness
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://hmmglobal.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 (675 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://hmmglobal.com/en/home-en all use the title “HMM Global”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://hmmglobal.com/home-care, https://hmmglobal.com/mobility, https://hmmglobal.com/servicios-tpa, https://hmmglobal.com/innovacion, https://hmmglobal.com/seguridad and https://hmmglobal.com/en/home-en and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://hmmglobal.com/home-care, https://hmmglobal.com/mobility, https://hmmglobal.com/servicios-tpa, https://hmmglobal.com/innovacion, https://hmmglobal.com/seguridad and https://hmmglobal.com/en/home-en and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://hmmglobal.com/contacto has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 7 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
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…”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
10 distorted images
10 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
6 of 6 tappable elements near the top are at least 24 px.
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.
A 8-field form
Your longest form asks for 8 fields (7 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.
Only about 190 words
The homepage has only about 190 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Solicitar demo”.
Social proof on the page
Social proof on the homepage: 9 testimonial or review blocks, 10 customer or partner logos and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
23 other companies contacted
Loading the homepage contacts 23 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 hmmglobal.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2022.
Stack
- CMS
- WordPress
- 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 46 issues on hmmglobal.com, including 17 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.