cvs.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 4.0 s

  4.0 s

  Real visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

• Real-user CLS: 0.21

  0.21

  For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.

• Real-user FCP: 2.6 s

  2.6 s

  Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

• Real-user TTFB: 1.6 s

  1.6 s

  Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

• Largest content (LCP) held steady for real visitors

  0%

  Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 4.0 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Page weight: 6.5 MB

  6.5 MB

  Your homepage downloads 6.5 MB on a phone, 1.3 MB of it images (19%). Under 2 MB keeps phones on slow connections fast.

• 11 images below the first screen load straight away

  11 images further down the page (474 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• 2 images far larger than shown

  69 KiB

  2 images are downloaded at several times the size a phone draws them, for example hero-main-overlap-bandages.png at 1,240 px wide, shown at 374 px. Resized copies would save about 69 KiB.

  Elements (2)

• About 1.8 g of CO₂ per visit

  1.83 g

  By the Sustainable Web Design model, a visit to your homepage emits about 1.83 g of CO₂e: 219.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

• 7 buttons without a name

  7 buttons have no accessible name, so screen readers announce just “button”.

  Elements (3)

• Images must have alternative text (2 elements)

  Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

  Elements (2)

• Hidden but focusable

  4 elements hidden from screen readers can still receive keyboard focus.

  Elements (3)

• 4 tap targets too small

  4 tap targets are too small or too close together to hit reliably with a finger.

  Elements (3)

• Form elements should have a visible label (1 element)

  Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• 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.

  Elements (1)

• 2 form fields without a label

  2 form fields have no label, so screen readers announce an empty box and autofill guesses.

• ARIA role should be appropriate for the element (5 elements)

  ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• Title is long (68 characters)

  Your title is 68 characters, so Google will cut it off around 60: “CVS - Online Drugstore, Pharmacy, Prescriptions & Health Information”.

  View source

• 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.

• Only 0 internal links

  The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is incomplete here.

• Parts of the site are closed to 1 AI crawler

  Your robots.txt lets ChatGPT (ChatGPT-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

• 4 JavaScript errors while loading

  4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  cvs.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  cvs.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• No calls to action

  We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• 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.

  View source

• No analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• Phone number is not tap-to-call

  Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

• 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.

• About 2,114 words of copy

  The homepage carries about 2,114 words of visible text.

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 85/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 1 tracker load before any consent

  1

  Before a visitor clicks anything, the page loads Google Ads (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

• 102 cookies set on arrival

  102

  Opening the homepage sets 102 cookies, 1 of them by other companies (measured from a US location before any click).

• 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.