Website review, no card needed
galileo.io website review
Visit site (opens in a new tab)Reviewed 3 November 202630 issues · 81 checks
This review found 30 issues worth fixing on galileo.io, 11 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 212 ms |
| May 23, 2026 | 213 ms |
| May 30, 2026 | 206 ms |
| Jun 6, 2026 | 204 ms |
| Jun 13, 2026 | 203 ms |
| Jun 20, 2026 | 193 ms |
| Jun 27, 2026 | 190 ms |
| Jul 4, 2026 | 183 ms |
| Jul 11, 2026 | 177 ms |
| Jul 18, 2026 | 178 ms |
| Jul 25, 2026 | 174 ms |
| Aug 1, 2026 | 176 ms |
| Aug 8, 2026 | 181 ms |
| Aug 15, 2026 | 185 ms |
| Aug 22, 2026 | 191 ms |
| Aug 29, 2026 | 192 ms |
| Sep 5, 2026 | 186 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 180 ms |
| Sep 26, 2026 | 178 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 170 ms |
| Oct 17, 2026 | 150 ms |
| Oct 24, 2026 | 134 ms |
| Oct 31, 2026 | 128 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
Speed
Render-blocking requests
2.6 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.2 s
A phone's processor spends 5.2 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 (Google Tag Manager, website-files.com and Clarity and others), adding 2.7 MB and 2.2 s of main-thread time.
Reduce unused JavaScript
700 ms · 787 KiBAbout 787 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 700 ms faster on a phone.
Google Tag Manager adds 756 ms
756 msGoogle Tag Manager costs a phone 756 ms of main-thread work and 974 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.
website-files.com adds 743 ms
743 mswebsite-files.com costs a phone 743 ms of main-thread work and 966 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.
Use efficient cache lifetimes
300 ms · 450 KiB26 files are served with short cache lifetimes, so returning visitors download them again (450 KiB).
Reduce unused CSS
450 ms · 68 KiBAbout 68 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 277 ms. During a long task the page ignores taps.
Improve image delivery
193 KiB8 images could be 193 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Duplicated JavaScript
50 KiB50 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need.
Minify JavaScript
36 KiB36 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: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bringing care closer. Traditional health care keeps your do…”.
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
Total Blocking Time: 949 ms
949 msScripts block taps and scrolling for 949 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 86 ms
86 msReal visitors wait 86 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: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 362 ms
362 msReal visitors wait 362 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 212 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 56% faster for real visitors
-56%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.042
0.042The layout barely moves while loading (CLS 0.042, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 119 requests
2.8 MBYour homepage downloads 2.8 MB in 119 requests on a phone: scripts 2.0 MB (52), images 472 KiB (21) and fonts 178 KiB (4). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 96.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 14 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
35 internal links, 6 external
The homepage links to 35 pages on galileo.io and 6 external pages.
7 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Access telehealth consultations for urgent needs and ongoing primary care. Talk to a licensed doctor anytime, anywhere …”.
One H1 headline
Your main headline reads: “Bringing care closer.”.
Title: 55 characters
Your title is a healthy 55 characters: “Virtual Care – 24/7 Urgent & Primary Services | Galileo”.
Canonical URL set
The canonical URL is https://galileo.io/.
Structured data in place
Structured data found: MedicalOrganization, WebPage and WebSite.
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://galileo.io/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: 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 (645 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://galileo.io/llms.txt (2 KiB, 18 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
/ and https://galileo.io/es all use the title “Virtual Care – 24/7 Urgent & Primary Services | Galileo”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://galileo.io/resources/press has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
5 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 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 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97223862&tm=gtm002&Ver=2&mid=a0f7eea0-9f51-4780-811e-101b3234cd47&bo=5&sid=cb844530d72411f1a9f06588aee16d5b&vid=cb8470f0d72411f19a4861e19c0bafb4&vids=1&msclkid=N>m_t.
5 small tap targets
5 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “[components] Finsweet Components - this Component is not available for production use. Please purchase a plan at https:…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 616 words of copy
The homepage carries about 616 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “How to try out Galileo for myself”.
2 calls to action
The homepage has 2 calls to action, for example “How to try out Galileo for myself” and “Learn more about our solutions”.
Analytics in place
Analytics detected: Google Tag Manager, Hotjar, HubSpot and Segment.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 6 mores (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.
35 cookies set on arrival
35Opening the homepage sets 35 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.
37 other companies contacted
Loading the homepage contacts 37 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 galileo.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Webflow
- Analytics
- Google Tag Manager | Hotjar | Segment
- Hosting
- Webflow
Hiring
- Hiring
- 3 open roles
- Job board
- careers page
- Careers page
- galileo.io/careers (opens in a new tab)
Company
- Employees
- 389
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on galileo.io, including 16 speed issues, 1 SEO issue 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.