Website review, no card needed
allianceptp.com website review
Visit site (opens in a new tab)Reviewed 19 October 202643 issues · 91 checks
This review found 43 issues worth fixing on allianceptp.com, 16 of them high impact, across 91 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.9 s |
| May 2, 2026 | 3.1 s |
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 93 ms |
| May 2, 2026 | 94 ms |
| May 9, 2026 | 98 ms |
| May 16, 2026 | 124 ms |
| May 23, 2026 | 124 ms |
| May 30, 2026 | 126 ms |
| Jun 6, 2026 | 137 ms |
| Jun 13, 2026 | 128 ms |
| Jun 20, 2026 | 124 ms |
| Jun 27, 2026 | 107 ms |
| Jul 4, 2026 | 98 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 102 ms |
| Aug 1, 2026 | 103 ms |
| Aug 8, 2026 | 101 ms |
| Aug 15, 2026 | 82 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 92 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 102 ms |
| Sep 19, 2026 | 101 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 88 ms |
| Oct 10, 2026 | 81 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
Reduce unused JavaScript
7.2 s · 988 KiBAbout 988 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.2 s faster on a phone.
Use efficient cache lifetimes
5.0 s · 820 KiB14 files are served with short cache lifetimes, so returning visitors download them again (820 KiB).
Render-blocking requests
5.2 s46 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.2 s.
Improve image delivery
1.4 s · 223 KiB5 images could be 223 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 70). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Google Maps and others), adding 2.0 MB and 767 ms of main-thread time.
Google CDN adds 320 ms
320 msGoogle CDN costs a phone 320 ms of main-thread work and 733 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
300 ms · 67 KiBAbout 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 287 ms
287 msGoogle Tag Manager costs a phone 287 ms of main-thread work and 539 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.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Maps adds 111 ms
111 msGoogle Maps costs a phone 111 ms of main-thread work and 427 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 · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 126 ms. During a long task the page ignores taps.
Minify JavaScript
12 KiB12 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: 27 ms
27 msYour server sent the HTML in 27 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 FCP: 3.2 s
3.2 sReal visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 14.6 s
14.6 sThe first text or image appears after 14.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 23.3 s
23.3 sYour largest element takes 23.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “STRONGER TOGETHER”.
Speed Index: 14.6 s
14.6 sVisually, the page fills in at 14.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 23.7 s
23.7 sThe page becomes fully interactive after 23.7 s. Good is under 3.8 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 207 ms
207 msScripts block taps and scrolling for 207 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.9 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 91 ms
91 msReal visitors wait 91 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 93 ms to 81 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.3 MB in 142 requests
4.3 MBYour homepage downloads 4.3 MB in 142 requests on a phone: scripts 2.0 MB (35), images 1.2 MB (13) and fonts 438 KiB (9). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
137 KiB1 image is downloaded at several times the size a phone draws it, for example AlliAnce-Advent.webp at 1,649 px wide, shown at 50 px. Resized copies would save about 137 KiB.
1 image in older formats
1 image (474 KiB) is 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.
3 images below the first screen load straight away
3 images further down the page (188 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 145.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA commands must have an accessible name (2 elements)
ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
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.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
42 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: 42 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (45 characters)
Your meta description is only 45 characters: “People. Integrity. Compassion. Relationships.”. 70 to 160 characters is enough to sell the click.
4 H1 headlines
There are 4 <h1> headlines (“Stronger Together”, “Partner With Alliance” and “Careers at Alliance Physical Therapy Partners”). One clear main headline is easier for people and search engines.
Structured data has 4 problems
Structured data found (Article, ImageObject, LocalBusiness and Organization) but with 4 problems, for example “Organization: logo is not an absolute URL ("https://allianceptp.com/wp-content/uploads/2024/12/Alliance_FINAL_TM-1.png")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://allianceptp.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at allianceptp.com/robots.txt, the first file search crawlers ask for.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
55 internal links, 15 external
The homepage links to 55 pages on allianceptp.com and 15 external pages.
2 checks passed
Title: 41 characters
Your title is a healthy 41 characters: “Home - Alliance Physical Therapy Partners”.
Canonical URL set
The canonical URL is https://allianceptp.com/.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://allianceptp.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (734 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://allianceptp.com/alliance-physical-therapy-earns-2026-great-place-to-work-certification, whose canonical is https://allianceptp.com/2026/04/15/alliance-physical-therapy-earns-2026-great-place-to-work-certification. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 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 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'mouse')”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
9 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 10-field form
Your longest form asks for 10 fields (8 required). Every extra field lowers completion.
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 478 words of copy
The homepage carries about 478 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Call Now”.
2 calls to action
The homepage has 2 calls to action, for example “Learn More” and “Call Now”.
Social proof on the page
Social proof on the homepage: 40 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
13 other companies contacted
Loading the homepage contacts 13 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 allianceptp.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on allianceptp.com, including 21 speed issues, 7 SEO issues and 1 conversion gap. 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.