Website review, no card needed
herabiotech.com website review
Visit site (opens in a new tab)Reviewed 5 November 202640 issues · 82 checks
This review found 40 issues worth fixing on herabiotech.com, 14 of them high impact, across 82 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
73CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.7 s
2.3 s
2.9 s
3.5 s
4.1 s
4.6 s
Speed
Use efficient cache lifetimes
12.1 s · 11.9 MB79 files are served with short cache lifetimes, so returning visitors download them again (11.9 MB).
Render-blocking requests
7.4 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.4 s.
Reduce unused CSS
5.1 s · 955 KiBAbout 955 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.1 s faster on a phone.
Reduce unused JavaScript
2.4 s · 549 KiBAbout 549 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Improve image delivery
850 ms · 8.7 MB15 images could be 8.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Vimeo and Google Fonts and others), adding 12.4 MB and 231 ms of main-thread time.
Vimeo adds 114 ms
114 msVimeo costs a phone 114 ms of main-thread work and 12.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.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Minify JavaScript
140 ms · 57 KiB57 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 27 KiB27 KiB could be saved by minifying CSS.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 108 ms. During a long task the page ignores taps.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 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.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 702 ms of it running JavaScript. That is comfortably low.
Server response: 62 ms
62 msYour server sent the HTML in 62 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 9.5 s
9.5 sThe first text or image appears after 9.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 21.0 s
21.0 sYour largest element takes 21.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NON-INVASIVE, TISSUE-BASED DIAGNOSTICS Diagnosing Endometri…”.
Time to Interactive: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
22 images without width and height
22 images have no width and height attributes, so the layout jumps as each one loads.
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.
2 checks passed
Total Blocking Time: 134 ms
134 msScripts block the page for only 134 ms while loading. Good is under 200 ms.
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: 24.3 MB in 116 requests
24.3 MBYour homepage downloads 24.3 MB in 116 requests on a phone: other files 11.6 MB (26), images 10.1 MB (23) and scripts 1.0 MB (36). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 8.9 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
7.7 MB6 images are downloaded at several times the size a phone draws them, for example packaing-metridx_image-5.png at 4,096 px wide, shown at 500 px. Resized copies would save about 7.7 MB.
11 images in older formats
11 images (9.7 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.
7 images below the first screen load straight away
7 images further down the page (9.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.9 g of CO₂ per visit
6.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.89 g of CO₂e: 827.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h1 → h4, h2 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://herabiotech.com/sitemap.xml, so Google discovers your pages only by following links.
30 internal links, 14 external
The homepage links to 30 pages on herabiotech.com and 14 external pages.
4 checks passed
Meta description: 73 characters
Your meta description is 73 characters: “Diagnosing Endometriosis and Cervical Cancer—In Tissue. On Time. For Her.”.
One H1 headline
Your main headline reads: “Diagnosing Endometriosis and Cervical Cancer”.
Title: 59 characters
Your title is a healthy 59 characters: “Hera Biotech - Diagnosing Endometriosis and Cervical Cancer”.
robots.txt in place
robots.txt is in place.
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://herabiotech.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 (647 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://herabiotech.com/platform, which answers with an error. Visitors hit a dead end and search engines drop it.
4 pages share a meta description
https://herabiotech.com/about, https://herabiotech.com/products, https://herabiotech.com/privacy-policy and https://herabiotech.com/terms-and-conditions use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://herabiotech.com/privacy-policy and https://herabiotech.com/terms-and-conditions have no <h1> headline, so visitors and search engines get no clear main topic.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 4 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
A 8-field form
Your longest form asks for 8 fields (8 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 490 words of copy
The homepage carries about 490 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: “[email protected]”.
10 calls to action
The homepage has 10 calls to action, for example “CONTACT”, “Learn More” and “Learn more about the conditions”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies, 2 of them by other companies (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 herabiotech.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
- Joomla
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Akamai Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on herabiotech.com, including 14 speed issues, 4 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.