Website review, no card needed
heal360.com website review
Visit site (opens in a new tab)Reviewed 20 October 202636 issues · 83 checks
This review found 36 issues worth fixing on heal360.com, 9 of them high impact, across 83 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 989 ms |
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 993 ms |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 100 ms |
| May 9, 2026 | 106 ms |
| May 16, 2026 | 119 ms |
| May 23, 2026 | 100 ms |
| May 30, 2026 | 133 ms |
| Jun 6, 2026 | 105 ms |
| Jun 13, 2026 | 111 ms |
| Jun 20, 2026 | 119 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 136 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 131 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 132 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 116 ms |
| Sep 19, 2026 | 116 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 148 ms |
| Oct 10, 2026 | 156 ms |
| Oct 17, 2026 | 162 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
1.8 s · 525 KiB10 images could be 525 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.3 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Use efficient cache lifetimes
150 ms · 2.7 MB14 files are served with short cache lifetimes, so returning visitors download them again (2.7 MB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, website-files.com and Facebook and others), adding 4.7 MB and 810 ms of main-thread time.
Mobile performance score: 68
68/100Your mobile performance score is 68 (desktop: 73). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 464 ms
464 msGoogle Tag Manager costs a phone 464 ms of main-thread work and 718 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.
Reduce unused CSS
450 ms · 81 KiBAbout 81 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.
Reduce unused JavaScript
491 KiBAbout 491 KiB of JavaScript is downloaded but never used on this page.
website-files.com adds 86 ms
86 mswebsite-files.com costs a phone 86 ms of main-thread work and 3.6 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 205 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 16 KiB16 KiB could be saved by minifying CSS.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
Minify JavaScript
15 KiB15 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.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 899 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 17.0 s
17.0 sThe page becomes fully interactive after 17.0 s. Good is under 3.8 s.
Largest Contentful Paint: 6.3 s
6.3 sYour largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Tap response (INP) got 54% slower for real visitors
+54%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 100 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
27 images without width and height
27 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 251 ms
251 msScripts block taps and scrolling for 251 ms in total while the page loads. Good is under 200 ms.
7 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: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 162 ms
162 msReal visitors wait 162 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: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 457 ms
457 msReal visitors wait 457 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Images and page weight
Page weight: 5.3 MB in 103 requests
5.3 MBYour homepage downloads 5.3 MB in 103 requests on a phone: media 2.5 MB (2), scripts 1.4 MB (41) and images 959 KiB (29). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (223 KiB) 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.
About 1.5 g of CO₂ per visit
1.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.51 g of CO₂e: 181.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
22 images without alt text
22 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 6 failed. 2 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.
Meta description is long (273 characters)
Your meta description is 273 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
29 internal links, 4 external
The homepage links to 29 pages on heal360.com and 4 external pages.
5 checks passed
One H1 headline
Your main headline reads: “How can our team help you get better?”.
Title: 56 characters
Your title is a healthy 56 characters: “Heal 360 Primary & Urgent Care Practices in the DFW Area”.
Canonical URL set
The canonical URL is https://www.heal360.com/.
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.heal360.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://www.heal360.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 (495 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://www.heal360.com/laser-treatment and https://www.heal360.com/forms/refill-request have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages with very little text
https://www.heal360.com/doctors and https://www.heal360.com/careers have 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187028311&tm=gtm002&Ver=2&mid=09dc86d1-fcb3-497b-904a-10be863e94bd&bo=1&sid=71bfb5f0cc7911f18cd8af90da1f6baa&vid=71bfd1c0cc7911f18c75d50c6853dbda&vids=1&msclkid=N>m_.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
8 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 366 words of copy
The homepage carries about 366 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: “Book”.
8 calls to action
The homepage has 8 calls to action, for example “Book”, “Book Appointment” and “Refill Request”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
32 other companies contacted
Loading the homepage contacts 32 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 heal360.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
- Webflow
- 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 36 issues on heal360.com, including 17 speed issues, 4 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.