Website review, no card needed
alpinepeds.com website review
Visit site (opens in a new tab)Reviewed 18 October 202648 issues · 86 checks
This review found 48 issues worth fixing on alpinepeds.com, 15 of them high impact, across 86 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 809 ms |
| May 2, 2026 | 778 ms |
| May 9, 2026 | 757 ms |
| May 16, 2026 | 778 ms |
| May 23, 2026 | 745 ms |
| May 30, 2026 | 721 ms |
| Jun 6, 2026 | 709 ms |
| Jun 13, 2026 | 727 ms |
| Jun 20, 2026 | 805 ms |
| Jun 27, 2026 | 813 ms |
| Jul 4, 2026 | 817 ms |
| Jul 11, 2026 | 817 ms |
| Jul 18, 2026 | 781 ms |
| Jul 25, 2026 | 705 ms |
| Aug 1, 2026 | 686 ms |
| Aug 8, 2026 | 687 ms |
| Aug 15, 2026 | 712 ms |
| Aug 22, 2026 | 706 ms |
| Aug 29, 2026 | 723 ms |
| Sep 5, 2026 | 696 ms |
| Sep 12, 2026 | 675 ms |
| Sep 19, 2026 | 736 ms |
| Sep 26, 2026 | 754 ms |
| Oct 3, 2026 | 787 ms |
| Oct 10, 2026 | 829 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 71 ms |
| May 2, 2026 | 73 ms |
| May 9, 2026 | 73 ms |
| May 16, 2026 | 75 ms |
| May 23, 2026 | 73 ms |
| May 30, 2026 | 72 ms |
| Jun 6, 2026 | 71 ms |
| Jun 13, 2026 | 73 ms |
| Jun 20, 2026 | 80 ms |
| Jun 27, 2026 | 80 ms |
| Jul 4, 2026 | 80 ms |
| Jul 11, 2026 | 79 ms |
| Jul 18, 2026 | 77 ms |
| Jul 25, 2026 | 79 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 78 ms |
| Aug 15, 2026 | 75 ms |
| Aug 22, 2026 | 71 ms |
| Aug 29, 2026 | 71 ms |
| Sep 5, 2026 | 75 ms |
| Sep 12, 2026 | 78 ms |
| Sep 19, 2026 | 77 ms |
| Sep 26, 2026 | 76 ms |
| Oct 3, 2026 | 72 ms |
| Oct 10, 2026 | 71 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
Use efficient cache lifetimes
4.0 s · 1.5 MB41 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Reduce unused JavaScript
3.8 s · 726 KiBAbout 726 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.
Render-blocking requests
2.4 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Reduce unused CSS
1.2 s · 163 KiBAbout 163 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 90). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
500 ms · 466 KiB22 images could be 466 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Minify JavaScript
780 ms · 136 KiB136 KiB could be saved by minifying JavaScript.
7 third-party services on the page
7 third-party services load with your homepage (chatpath.com, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.0 MB and 715 ms of main-thread time.
chatpath.com adds 493 ms
493 mschatpath.com costs a phone 493 ms of main-thread work and 752 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 557 ms. During a long task the page ignores taps.
Document request latency
34 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Phones get a much slower page than desktops
Desktop scores 90 but mobile only 48. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
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, 836 ms of it running JavaScript. That is comfortably low.
Server response: 26 ms
26 msYour server sent the HTML in 26 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.
Largest Contentful Paint: 15.8 s
15.8 sYour largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 11.9 s
11.9 sVisually, the page fills in at 11.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.6 s
5.6 sThe first text or image appears after 5.6 s on a phone. Good is under 1.8 s.
Time to Interactive: 16.8 s
16.8 sThe page becomes fully interactive after 16.8 s. Good is under 3.8 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Total Blocking Time: 346 ms
346 msScripts block taps and scrolling for 346 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 71 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 74 ms
74 msReal visitors wait 74 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 619 ms
619 msReal visitors wait 619 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.05
0.05The layout barely moves while loading (CLS 0.05, good is under 0.1).
Images and page weight
Page weight: 2.6 MB in 77 requests
2.6 MBYour homepage downloads 2.6 MB in 77 requests on a phone: scripts 1.4 MB (11), images 949 KiB (34) and stylesheets 196 KiB (5). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (288 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.
8 images below the first screen load straight away
8 images further down the page (275 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.72 g of CO₂e: 86.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
<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.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
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
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 28 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (227 characters)
Your title is 227 characters, so Google will cut it off around 60: “Alpine Pediatrics - Pediatricians serving Northern Utah County with offices in Pleasant G…”.
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:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://alpinepeds.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at alpinepeds.com/robots.txt, the first file search crawlers ask for.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
135 internal links, 5 external
The homepage links to 135 pages on alpinepeds.com and 5 external pages.
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://alpinepeds.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 (356 words), so crawlers that don't run JavaScript still read it.
Other pages
13 pages share a title
https://alpinepeds.com/patient_portal.html, https://alpinepeds.com/locations.html, https://alpinepeds.com/location_pg.html, https://alpinepeds.com/location_lw.html, https://alpinepeds.com/location_le.html and https://alpinepeds.com/location_sspx.html and 7 others all use the title “Alpine Pediatrics - Pediatricians serving Northern Utah County with o…”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://alpinepeds.com/patient_portal.html, https://alpinepeds.com/locations.html, https://alpinepeds.com/location_pg.html, https://alpinepeds.com/location_lw.html, https://alpinepeds.com/location_le.html and https://alpinepeds.com/location_sspx.html and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://alpinepeds.com/patient_portal.html, https://alpinepeds.com/locations.html, https://alpinepeds.com/location_pg.html, https://alpinepeds.com/location_lw.html, https://alpinepeds.com/location_le.html and https://alpinepeds.com/location_sspx.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.
4 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.
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
20 small tap targets
20 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks 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
Thin social proof
Social proof on the homepage: 4 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.
Only about 205 words
The homepage has only about 205 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “MED REFILL REQUEST” and “CONTACT US”.
10 calls to action
The homepage has 10 calls to action, for example “Med Refill Request”, “Contact Us” and “Schedule Apppointment”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Mixpanel (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 (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.
10 other companies contacted
Loading the homepage contacts 10 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 alpinepeds.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
- Bootstrap
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on alpinepeds.com, including 18 speed issues, 9 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.