Website review, no card needed
brushandfloss.com website review
Visit site (opens in a new tab)Reviewed 28 October 202624 issues · 85 checks
This review found 24 issues worth fixing on brushandfloss.com, 13 of them high impact, across 85 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 96 ms |
| May 16, 2026 | 95 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 98 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 93 ms |
| Aug 22, 2026 | 88 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 88 ms |
| Sep 12, 2026 | 88 ms |
| Sep 19, 2026 | 91 ms |
| Sep 26, 2026 | 92 ms |
| Oct 3, 2026 | 92 ms |
| Oct 10, 2026 | 93 ms |
| Oct 17, 2026 | 94 ms |
| Oct 24, 2026 | 95 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.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
Reduce unused JavaScript
2.4 s · 427 KiBAbout 427 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Google Tag Manager adds 2.2 s
2.2 sGoogle Tag Manager costs a phone 2.2 s of main-thread work and 841 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
2.3 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Mobile performance score: 34
34/100Your mobile performance score is 34 (desktop: 86). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, website-files.com and cloudfront.net and others), adding 2.5 MB and 2.7 s of main-thread time.
Improve image delivery
200 ms · 1.1 MB10 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.
website-files.com adds 234 ms
234 mswebsite-files.com costs a phone 234 ms of main-thread work and 1.4 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.
1,741 HTML elements
The page has 1,741 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 47 KiBAbout 47 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.
Legacy JavaScript
150 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Use efficient cache lifetimes
50 ms · 21 KiB9 files are served with short cache lifetimes, so returning visitors download them again (21 KiB).
Phones get a much slower page than desktops
Desktop scores 86 but mobile only 34. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.7 s
13.7 sYour largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Riccobene Associates dental team”.
Time to Interactive: 15.7 s
15.7 sThe page becomes fully interactive after 15.7 s. Good is under 3.8 s.
First Contentful Paint: 5.2 s
5.2 sThe first text or image appears after 5.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 96 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 106 ms
106 msReal visitors wait 106 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 341 ms
341 msReal visitors wait 341 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.2 s 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: 2.8 MB in 79 requests
2.8 MBYour homepage downloads 2.8 MB in 79 requests on a phone: images 1.2 MB (21), scripts 1.1 MB (23) and fonts 367 KiB (20). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (460 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.8 g of CO₂ per visit
0.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 95.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
27 text elements with low contrast
27 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
23 tap targets too small
23 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 124 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Riccobene Associates Family Dentistry | Dentists in North Carolina”.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
128 internal links, 7 external
The homepage links to 128 pages on brushandfloss.com and 7 external pages.
7 checks passed
Meta description: 120 characters
Your meta description is 120 characters: “Riccobene Associates Family Dentistry delivers top-notch dental care to families and patients throughout North Carolina.”.
One H1 headline
Your main headline reads: “Comprehensive Family Dentistry Near You”.
Canonical URL set
The canonical URL is https://www.brushandfloss.com/.
Structured data in place
Structured data found: Brand, Dentist, Organization, Review and SiteNavigationElement.
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.brushandfloss.com/sitemap.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (3,586 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.brushandfloss.com/llms.txt (15 KiB, 92 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 86 found) and read each the way a search engine does.
7 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.
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
6 small tap targets
6 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 1,887 words of copy
The homepage carries about 1,887 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”.
6 calls to action
The homepage has 6 calls to action, for example “Schedule an appointment”, “Contact Us” and “Book an appointment”.
Social proof on the page
Social proof on the homepage: 63 testimonial or review blocks, 12 customer or partner logos, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 57 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
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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
24 other companies contacted
Loading the homepage contacts 24 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 brushandfloss.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 24 issues on brushandfloss.com, including 15 speed issues and 2 SEO 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.