Website review, no card needed
herofutureenergies.com website review
Visit site (opens in a new tab)Reviewed 30 October 202644 issues · 89 checks
This review found 44 issues worth fixing on herofutureenergies.com, 21 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.8 s |
| May 16, 2026 | 3.8 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 4.0 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 4.3 s |
| Oct 24, 2026 | 4.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 112 ms |
| May 16, 2026 | 111 ms |
| May 23, 2026 | 116 ms |
| May 30, 2026 | 116 ms |
| Jun 6, 2026 | 115 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 99 ms |
| Jul 25, 2026 | 101 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 108 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 116 ms |
| Aug 29, 2026 | 116 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 117 ms |
| Sep 19, 2026 | 118 ms |
| Sep 26, 2026 | 118 ms |
| Oct 3, 2026 | 115 ms |
| Oct 10, 2026 | 118 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 108 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
1.8 s
3.6 s
5.4 s
7.2 s
9.1 s
10.9 s
12.7 s
14.5 s
Speed
Use efficient cache lifetimes
8.9 s · 10.5 MB59 files are served with short cache lifetimes, so returning visitors download them again (10.5 MB).
Improve image delivery
6.5 s · 4.3 MB15 images could be 4.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.5 s faster on a phone.
Reduce unused JavaScript
6.2 s · 628 KiBAbout 628 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.2 s faster on a phone.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Render-blocking requests
2.2 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 third-party services on the page
6 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.4 MB and 904 ms of main-thread time.
Google CDN adds 694 ms
694 msGoogle CDN costs a phone 694 ms of main-thread work and 1.1 MB 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.
Reduce unused CSS
450 ms · 50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 158 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 1 ms
1 msYour server sent the HTML in 1 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: 5.9 s
5.9 sReal visitors wait 5.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.1 s
4.1 sReal visitors see the first content after 4.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.2 s
3.2 sReal visitors wait 3.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 24.6 s
24.6 sYour largest element takes 24.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 20.3 s
20.3 sVisually, the page fills in at 20.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 33.8 s
33.8 sThe page becomes fully interactive after 33.8 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.593
0.593The layout shifts by 0.593 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 374 ms
374 msScripts block taps and scrolling for 374 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 108 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.8 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 108 ms
108 msReal visitors wait 108 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 12.3 MB in 80 requests
12.3 MBYour homepage downloads 12.3 MB in 80 requests on a phone: images 10.2 MB (46), scripts 1.3 MB (13) and other files 350 KiB (2). Under 2 MB keeps phones on slow connections fast.
13 images over 500 KB
13 images weigh 11.0 MB together. On a phone connection a single image that size takes seconds.
9 images far larger than shown
4.3 MB9 images are downloaded at several times the size a phone draws them, for example Investor-RELATIONS.jpg at 3,839 px wide, shown at 414 px. Resized copies would save about 4.3 MB.
27 images in older formats
27 images (14.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.
12 images below the first screen load straight away
12 images further down the page (6.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.5 g of CO₂ per visit
3.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.47 g of CO₂e: 416.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (5 elements)
Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (42 elements)
All page content should be contained by landmarks: 42 elements on the page fail this check, rated moderate by axe-core.
7 form fields without a label
7 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h1 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 50 images in the HTML carry an alt attribute.
46 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: 46 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Leading Global Renewable & Green Energy Company | Hero Future Energies”.
Meta description is long (220 characters)
Your meta description is 220 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.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 links crawlers can't follow
2 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.
79 internal links, 20 external
The homepage links to 79 pages on herofutureenergies.com and 20 external pages.
5 checks passed
One H1 headline
Your main headline reads: “SHAPING A SUSTAINABLE FUTURE CLEAN ENERGY AND BEYOND……”.
Canonical URL set
The canonical URL is https://www.herofutureenergies.com/.
Structured data in place
Structured data found: Organization.
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.herofutureenergies.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.herofutureenergies.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,675 words), so crawlers that don't run JavaScript still read it.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.herofutureenergies.com/global-presence-vietnam, whose canonical is https://www.herofutureenergies.com/global-presence-south-east-asia. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages slow to respond
https://www.herofutureenergies.com/about-us, https://www.herofutureenergies.com/awards and https://www.herofutureenergies.com/utility-scale-projects took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
2 small tap targets
2 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “GLightbox is not defined”.
13 distorted images
13 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 1,205 words of copy
The homepage carries about 1,205 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us” and “Contact Investor Relations”.
2 short forms
2 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
7 other companies contacted
Loading the homepage contacts 7 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 herofutureenergies.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- AWS
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 herofutureenergies.com, including 22 speed issues, 5 SEO issues and 3 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.