Website review, no card needed

crestoralbproshop.com logo

crestoralbproshop.com website review

Visit site (opens in a new tab)Reviewed 25 October 202640 issues · 82 checks

This review found 40 issues worth fixing on crestoralbproshop.com, 12 of them high impact, across 82 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.6 s2.0 sMay 2Oct 172.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
141 ms118 msMay 2Oct 17135 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026137 ms
May 9, 2026137 ms
May 16, 2026132 ms
May 23, 2026134 ms
May 30, 2026134 ms
Jun 6, 2026129 ms
Jun 13, 2026129 ms
Jun 20, 2026129 ms
Jun 27, 2026129 ms
Jul 4, 2026127 ms
Jul 11, 2026127 ms
Jul 18, 2026125 ms
Jul 25, 2026121 ms
Aug 1, 2026128 ms
Aug 8, 2026129 ms
Aug 15, 2026129 ms
Aug 22, 2026130 ms
Aug 29, 2026131 ms
Sep 5, 2026130 ms
Sep 12, 2026136 ms
Sep 19, 2026133 ms
Sep 26, 2026129 ms
Oct 3, 2026137 ms
Oct 10, 2026138 ms
Oct 17, 2026135 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

Full-page screenshot of crestoralbproshop.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. crestoralbproshop.com at 0.9 s0.9 s
  2. crestoralbproshop.com at 1.7 s1.7 s
  3. crestoralbproshop.com at 2.6 s2.6 s
  4. crestoralbproshop.com at 3.4 s3.4 s
  5. crestoralbproshop.com at 4.3 s4.3 s
  6. crestoralbproshop.com at 5.2 s5.2 s
  7. crestoralbproshop.com at 6.0 s6.0 s
  8. crestoralbproshop.com at 6.9 s6.9 s

Speed

12 to fix17
  • Render-blocking requests

    4.8 s

    18 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.

  • Reduce unused JavaScript

    1.8 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Mobile performance score: 17

    17/100

    Your mobile performance score is 17 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.2 s

    A phone's processor spends 5.2 s on main-thread work while loading, 3.3 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, Azure Web Services and Google CDN and others), adding 5.5 MB and 2.4 s of main-thread time.

  • Azure Web Services adds 667 ms

    667 ms

    Azure Web Services costs a phone 667 ms of main-thread work and 3.3 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.

  • Reduce unused CSS

    750 ms · 200 KiB

    About 200 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Google Tag Manager adds 834 ms

    834 ms

    Google Tag Manager costs a phone 834 ms of main-thread work and 529 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 CDN adds 499 ms

    499 ms

    Google CDN costs a phone 499 ms of main-thread work and 1.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

    150 ms · 358 KiB

    26 files are served with short cache lifetimes, so returning visitors download them again (358 KiB).

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 404 ms. During a long task the page ignores taps.

  • Improve image delivery

    334 KiB

    3 images could be 334 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    150 ms · 50 KiB

    Polyfills for old browsers add 50 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 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • Phones get a much slower page than desktops

    Desktop scores 46 but mobile only 17. 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.

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 23.2 s

    23.2 s

    Your largest element takes 23.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PREMIUM CREST + ORAL-B PRODUCTS FOR DENTAL PROFESSIONALS”.

  • Time to Interactive: 35.5 s

    35.5 s

    The page becomes fully interactive after 35.5 s. Good is under 3.8 s.

  • Speed Index: 13.9 s

    13.9 s

    Visually, the page fills in at 13.9 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 4.8 s

    4.8 s

    The first text or image appears after 4.8 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 1.4 s

    1.4 s

    Scripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.

  • Cumulative Layout Shift: 0.276

    0.276

    The layout shifts by 0.276 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user CLS: 0.23

    0.23

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

  • Largest content (LCP) got 20% slower for real visitors

    +20%

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • 10 images without width and height

    10 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 137 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 121 ms

    121 ms

    Real visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Images and page weight

3 to fix53
  • Page weight: 6.1 MB in 154 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 154 requests on a phone: scripts 4.4 MB (61), fonts 480 KiB (11) and images 464 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    2026on_2.webp 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).

  • 2 images far larger than shown

    86 KiB

    2 images are downloaded at several times the size a phone draws them, for example hygienist_with_Patient_in_chair_1_265971385.webp at 1,799 px wide, shown at 360 px. Resized copies would save about 86 KiB.

  • About 1.7 g of CO₂ per visit

    1.73 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

2 to fixGoogle 9998
  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • 3 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 26 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 2 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9282
  • 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 (56 characters)

    Your meta description is only 56 characters: “Premium Crest + Oral-B Products for Dental Professionals”. 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.

  • 62 internal links, 9 external

    The homepage links to 62 pages on crestoralbproshop.com and 9 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Premium Crest + Oral-B products for dental professionals”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Premium Crest + Oral-B Products for Dental Professionals”.

  • 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://crestoralbproshop.com/media/sitemap_robots/sitemap.xml.

AI search readiness

1 to fix88
  • 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://crestoralbproshop.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 (506 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    / and https://crestoralbproshop.com/conventions.html all use the title “Premium Crest + Oral-B Products for Dental Professionals”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://crestoralbproshop.com/specials has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.

5 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 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

2 to fixGoogle 8887
  • 8 small tap targets

    8 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://geolocation.onetrust.com/cookieconsentpub/v1/geo/location' violates the following Content Securi…”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • Only about 211 words

    The homepage has only about 211 words of visible text; thin pages give Google and first-time buyers little to go on.

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Register”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Register” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies (measured from a US location before any click).

  • 25 other companies contacted

    Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 crestoralbproshop.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

Framework
Bootstrap
E-commerce
Magento
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on crestoralbproshop.com, including 24 speed issues, 5 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25