Website review, no card needed
weccles.com website review
Visit site (opens in a new tab)Reviewed 22 November 202635 issues · 82 checks
This review found 35 issues worth fixing on weccles.com, 12 of them high impact, across 82 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
78CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
12.3 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.3 s faster on a phone.
Improve image delivery
1.8 s · 857 KiB3 images could be 857 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Maps and Google Tag Manager and others), adding 3.8 MB and 1.1 s of main-thread time.
Reduce unused CSS
900 ms · 196 KiBAbout 196 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
YouTube adds 706 ms
706 msYouTube costs a phone 706 ms of main-thread work and 2.1 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.
Use efficient cache lifetimes
450 ms · 87 KiB18 files are served with short cache lifetimes, so returning visitors download them again (87 KiB).
Render-blocking requests
450 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Maps adds 185 ms
185 msGoogle Maps costs a phone 185 ms of main-thread work and 483 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.
Google Tag Manager adds 112 ms
112 msGoogle Tag Manager costs a phone 112 ms of main-thread work and 295 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.
Google Fonts adds 2 ms
2 msGoogle Fonts costs a phone 2 ms of main-thread work and 769 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.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 91 ms
91 msYour server sent the HTML in 91 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 13.9 s
13.9 sThe first text or image appears after 13.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 36.9 s
36.9 sYour largest element takes 36.9 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: 15.5 s
15.5 sVisually, the page fills in at 15.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 37.8 s
37.8 sThe page becomes fully interactive after 37.8 s. Good is under 3.8 s.
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.
2 checks passed
Total Blocking Time: 133 ms
133 msScripts block the page for only 133 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.053
0.053The layout barely moves while loading (CLS 0.053, good is under 0.1).
Images and page weight
Page weight: 7.6 MB in 133 requests
7.6 MBYour homepage downloads 7.6 MB in 133 requests on a phone: images 3.5 MB (31), scripts 2.8 MB (43) and fonts 879 KiB (16). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.8 MB together. On a phone connection a single image that size takes seconds.
7 images in older formats
7 images (3.3 MB) 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.
1 image below the first screen load straight away
1 image further down the page (1.9 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
3 images far larger than shown
467 KiB3 images are downloaded at several times the size a phone draws them, for example Transition-to-Dr-Mark-2.png at 1,024 px wide, shown at 314 px. Resized copies would save about 467 KiB.
About 2.2 g of CO₂ per visit
2.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.16 g of CO₂e: 259.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (78 elements)
All page content should be contained by landmarks: 78 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.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 89 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
19 links with vague text
19 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
84 internal links, 8 external
The homepage links to 84 pages on weccles.com and 8 external pages.
8 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “Livermore holistic and biological dentist providing health centered mercury-free dental care for all your family member…”.
One H1 headline
Your main headline reads: “BIOLOGICAL DENTISTRY”.
Title: 44 characters
Your title is a healthy 44 characters: “Holistic and biological dentist in Livermore”.
Canonical URL set
The canonical URL is https://weccles.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://weccles.com/sitemap_index.xml.
AI search readiness
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, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,144 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a meta description
https://weccles.com/dental-surgery, https://weccles.com/tmj-therapy, https://weccles.com/ozone-therapy and https://weccles.com/dental-blog use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/6df33eff8c.css?ver=1.4.7' from origin 'https://weccles.com' ha…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
About 1,847 words of copy
The homepage carries about 1,847 words of visible text.
5 checks passed
3 calls to action
The homepage has 3 calls to action, for example “CONTACT” and “Learn More”.
Social proof on the page
Social proof on the homepage: 61 testimonial or review blocks and 66 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 1 of them by other companies (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.
17 other companies contacted
Loading the homepage contacts 17 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 weccles.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
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- NewtekOne, Inc.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on weccles.com, including 16 speed issues, 1 SEO issue and 2 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.