Website review, no card needed
justforkidsdental.com website review
Visit site (opens in a new tab)Reviewed 13 November 202620 issues · 74 checks
This review found 20 issues worth fixing on justforkidsdental.com, 7 of them high impact, across 74 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
84BClosest 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 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Reduce unused JavaScript
1.1 s · 199 KiBAbout 199 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Use efficient cache lifetimes
150 ms · 11.3 MB11 files are served with short cache lifetimes, so returning visitors download them again (11.3 MB).
8 third-party services on the page
8 third-party services load with your homepage (website-files.com, Google Tag Manager and cloudfront.net and others), adding 11.9 MB and 336 ms of main-thread time.
website-files.com adds 211 ms
211 mswebsite-files.com costs a phone 211 ms of main-thread work and 11.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.
Mobile performance score: 74
74/100Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
91 KiB2 images could be 91 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 67 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
30 ms · 14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 30 ms faster on a phone.
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: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 440 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: 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.
Time to Interactive: 6.3 s
6.3 sThe page becomes fully interactive after 6.3 s. Good is under 3.8 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
4 images without width and height
4 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
Speed Index: 2.4 s
2.4 sVisually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 36 ms
36 msScripts block the page for only 36 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 12.1 MB in 46 requests
12.1 MBYour homepage downloads 12.1 MB in 46 requests on a phone: media 11.2 MB (4), scripts 536 KiB (14) and images 204 KiB (10). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
63766cce2f9bfeefba24e218_Path 3.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 3.4 g of CO₂ per visit
3.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.43 g of CO₂e: 411.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 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.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
20 internal links, 7 external
The homepage links to 20 pages on justforkidsdental.com and 7 external pages.
8 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Just for Kids Dental is a welcoming pediatric dental office providing gentle, specialized care for children in a fun, p…”.
One H1 headline
Your main headline reads: “Family-Owned Pediatric Dentist inWaxahachie, TX”.
Title: 60 characters
Your title is a healthy 60 characters: “Pediatric Dentistry in Waxahachie, TX | Just for Kids Dental”.
Canonical URL set
The canonical URL is https://www.justforkidsdental.com/.
Structured data in place
Structured data found: Dentist.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.justforkidsdental.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.justforkidsdental.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (551 words), so crawlers that don't run JavaScript still read it.
Other pages
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
7 checks passed
Linked pages load
All 11 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 11 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 11 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 366 words of copy
The homepage carries about 366 words of visible text.
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “request an appointment”.
3 calls to action
The homepage has 3 calls to action, for example “request an appointment”.
1 short form
A short form (4 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links 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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
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.
12 other companies contacted
Loading the homepage contacts 12 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 justforkidsdental.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
- Hosting
- Webflow
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on justforkidsdental.com, including 10 speed issues. 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.