Website review, no card needed
pm-pediatrics.com website review
Visit site (opens in a new tab)Reviewed 20 November 202631 issues · 79 checks
This review found 31 issues worth fixing on pm-pediatrics.com, 8 of them high impact, across 79 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 sideOne 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
Render-blocking requests
1.5 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 84
84/100Your mobile performance score is 84. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
200 ms · 118 KiB25 files are served with short cache lifetimes, so returning visitors download them again (118 KiB).
Reduce unused JavaScript
150 ms · 29 KiBAbout 29 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
82 KiB7 images could be 82 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (Bootstrap CDN and prosites.com), adding 188 KiB and 2 ms of main-thread time.
Minify JavaScript
6 KiB6 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.
2 checks passed
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 126 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
Largest Contentful Paint: 3.5 s
3.5 sYour largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Time to Interactive: 3.6 s
3.6 sThe page is fully interactive after 3.6 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 5 ms
5 msScripts block the page for only 5 ms while loading. Good is under 200 ms.
Images and page weight
3 images in older formats
3 images (161 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 0.1 g of CO₂ per visit
0.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.12 g of CO₂e: 13.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 417 KiB in 38 requests
417 KiBYour homepage downloads 417 KiB in 38 requests on a phone: images 236 KiB (18), scripts 133 KiB (10) and stylesheets 37 KiB (6). That is a lean page.
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
Images must have alternative text (6 elements)
Images must have alternative text: 6 elements on the page fail this check, rated critical by axe-core.
3 text elements with low contrast
3 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 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.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Lewisville TX Pediatrics | PM Pediatrics | Lewisville TX Adolescent Medicine”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“PM Pediatrics”, “” and “Lewisville, TX Pediatrics & Adolescent Medicine”). One clear main headline is easier for people and search engines.
Meta description is long (218 characters)
Your meta description is 218 characters; Google truncates after about 160, so the end of your pitch is cut.
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 favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
11 internal links, 1 external
The homepage links to 11 pages on pm-pediatrics.com and 1 external page.
2 checks passed
Canonical URL set
The canonical URL is https://www.pm-pediatrics.com/.
XML sitemap found
Your XML sitemap is reachable at https://www.pm-pediatrics.com/sitemap.xml.
AI search readiness
robots.txt blocks 2 AI answer engine crawlers
2 of 6Your robots.txt shuts out Claude (Claude-User) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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.pm-pediatrics.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.
Opted out of AI training for 4 crawlers
robots.txt blocks GPTBot, ClaudeBot, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (274 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a meta description
https://www.pm-pediatrics.com/our-practice, https://www.pm-pediatrics.com/new-patient-info, https://www.pm-pediatrics.com/services and https://www.pm-pediatrics.com/contact use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://www.pm-pediatrics.com/our-practice, https://www.pm-pediatrics.com/new-patient-info and https://www.pm-pediatrics.com/contact have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.pm-pediatrics.com/services and https://www.pm-pediatrics.com/contact 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.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 4 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 a meta description
All 4 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
9 small tap targets
9 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://www.pm-pediatrics.com/' was loaded over HTTPS, but requested an insecure font 'http…”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
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 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 277 words of copy
The homepage carries about 277 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
2 calls to action
The homepage has 2 calls to action, for example “contact us” and “Contact”.
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Matomo.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 pm-pediatrics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on pm-pediatrics.com, including 6 speed issues, 8 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.