pedialliance.com website review

About 506 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.7 s.

Your mobile performance score is 33 (desktop: 79). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

18 files are served with short cache lifetimes, so returning visitors download them again (69 KiB).

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Constant Contact and others), adding 962 KiB and 784 ms of main-thread time.

Google Tag Manager costs a phone 542 ms of main-thread work and 505 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.

About 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 350 ms faster on a phone.

7 long tasks block the main thread while loading, the longest for 300 ms. During a long task the page ignores taps.

Google CDN costs a phone 144 ms of main-thread work and 347 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.

7 images could be 186 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

Desktop scores 79 but mobile only 33. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Trusted Pediatric Reviews”.

The first text or image appears after 6.0 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 15.2 s. Good is under 3.8 s.

The layout shifts by 0.304 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 858 ms for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 345 ms in total while the page loads. Good is under 200 ms.

11 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 2.3 MB in 98 requests on a phone: scripts 1.0 MB (20), other files 638 KiB (47) and images 338 KiB (15). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 79.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

59 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

57 tap targets are too small or too close together to hit reliably with a finger.

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.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

Your title is 88 characters, so Google will cut it off around 60: “Tampa Bay’s Best Pediatricians - Primary Care - Pediatric Urgent Care - Prenatal Visits.”.

Your meta description is 180 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 190 pages on pedialliance.com and 9 external pages.

There is no https://pedialliance.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.

https://pedialliance.com/locations and https://pedialliance.com/office-hours all use the title “Locations | Pediatric Health Care Alliance P.A.”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://pedialliance.com/forms/complimentary-prenatal-meeting, https://pedialliance.com/patient-forms, https://pedialliance.com/locations, https://pedialliance.com/forms/new-patient-welcome-meeting and https://pedialliance.com/office-hours have no meta description, so Google writes the search snippet from whatever text it finds.

https://pedialliance.com/pediatric-health-care-alliance-evening-weekend-hours, https://pedialliance.com/pediatric-urgent-care-evening-offices and https://pedialliance.com/evening-weekend-hours use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://pedialliance.com/pediatric-health-care-alliance-evening-weekend-hours, whose canonical is https://pedialliance.com/pediatric-urgent-care-evening-offices. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 15 pages linked from your homepage (of 79 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v6.4.0/css/all.css' from origin 'https://pedialliance…”.

3 images are served at too low a resolution for sharp phone screens.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 910 words of visible text.

Before 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.

Opening the homepage sets 12 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.