Website review, no card needed
thriftywhite.com website review
Visit site (opens in a new tab)Reviewed 29 October 202632 issues · 72 checks
This review found 32 issues worth fixing on thriftywhite.com, 11 of them high impact, across 72 checks. The most urgent: use efficient cache lifetimes. 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
77CClosest 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
Use efficient cache lifetimes
2.2 s · 855 KiB24 files are served with short cache lifetimes, so returning visitors download them again (855 KiB).
Render-blocking requests
2.1 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Improve image delivery
1.1 s · 497 KiB14 images could be 497 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Reduce unused CSS
1.1 s · 57 KiBAbout 57 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 144 KiBAbout 144 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and userway.org and others), adding 582 KiB and 320 ms of main-thread time.
Legacy JavaScript
150 ms · 31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 80 ms. During a long task the page ignores taps.
Document request latency
17 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 379 ms of it running JavaScript. That is comfortably low.
Server response: 35 ms
35 msYour server sent the HTML in 35 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.3 s
10.3 sYour largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Thrifty White Pharmacy”.
First Contentful Paint: 4.0 s
4.0 sThe first text or image appears after 4.0 s on a phone. Good is under 1.8 s.
Time to Interactive: 10.4 s
10.4 sThe page becomes fully interactive after 10.4 s. Good is under 3.8 s.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
12 images without width and height
12 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.
2 checks passed
Total Blocking Time: 68 ms
68 msScripts block the page for only 68 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
8 images below the first screen load straight away
8 images further down the page (319 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
6 images in older formats
6 images (331 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.4 g of CO₂ per visit
0.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.42 g of CO₂e: 50.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.5 MB in 55 requests
1.5 MBYour homepage downloads 1.5 MB in 55 requests on a phone: images 668 KiB (17), scripts 530 KiB (15) and fonts 189 KiB (3). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Links look like plain text
3 links inside paragraphs rely on colour alone to stand out.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (33 characters)
Your meta description is only 33 characters: “Welcome to Thrifty White Pharmacy”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
41 internal links, 5 external
The homepage links to 41 pages on thriftywhite.com and 5 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Thrifty White Pharmacy”.
Title: 59 characters
Your title is a healthy 59 characters: “Thrifty White Pharmacy - Prescriptions & Quality Healthcare”.
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.thriftywhite.com/sitemap.xml.
AI search readiness
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://thriftywhite.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (523 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://thriftywhite.com/current-ad has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://thriftywhite.com/online-bill-pay is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://thriftywhite.com/current-ad has no meta description, so Google writes the search snippet from whatever text it finds.
12 pages share a meta description
https://thriftywhite.com/locations, https://thriftywhite.com/online-refill, https://thriftywhite.com/patients, https://thriftywhite.com/specialty, https://thriftywhite.com/providers and https://thriftywhite.com/payors and 6 others use the same meta description. A description written for each page earns more clicks.
4 pages without an H1
https://thriftywhite.com/current-ad, https://thriftywhite.com/online-bill-pay, https://thriftywhite.com/schedule-testing and https://thriftywhite.com/schedule-vaccine have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
3 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.
Titles are unique
Every page we checked has its own title.
Best practices
12 small tap targets
12 of 19 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 “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.13.0/css/all.css' from origin 'https://thriftywhit…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 463 words of copy
The homepage carries about 463 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “schedule now”.
7 calls to action
The homepage has 7 calls to action, for example “Shop”, “CONTACT US” and “schedule now”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 (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.
15 other companies contacted
Loading the homepage contacts 15 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 thriftywhite.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Level3
Company
- Employees
- 892
- Founded
- 1884
- Headquarters
- Plymouth
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on thriftywhite.com, including 11 speed issues, 5 SEO issues 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.