Website review, no card needed

oralcare.bg logo

oralcare.bg website review

Visit site (opens in a new tab)Reviewed 20 November 202650 issues · 88 checks

This review found 50 issues worth fixing on oralcare.bg, 18 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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.3 s1.1 sMay 30Nov 141.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Oct 10, 20261.5 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Nov 7, 20261.4 s
Nov 14, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
116 ms75 msMay 30Nov 786 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202680 ms
Jun 6, 202686 ms
Jun 20, 2026111 ms
Oct 17, 202684 ms
Oct 24, 202684 ms
Oct 31, 202687 ms
Nov 7, 202686 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 oralcare.bg (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. oralcare.bg at 0.9 s0.9 s
  2. oralcare.bg at 1.8 s1.8 s
  3. oralcare.bg at 2.7 s2.7 s
  4. oralcare.bg at 3.5 s3.5 s
  5. oralcare.bg at 4.4 s4.4 s
  6. oralcare.bg at 5.3 s5.3 s
  7. oralcare.bg at 6.2 s6.2 s
  8. oralcare.bg at 7.1 s7.1 s

Speed

13 to fix50
  • Use efficient cache lifetimes

    20.8 s · 8.1 MB

    160 files are served with short cache lifetimes, so returning visitors download them again (8.1 MB).

  • Improve image delivery

    5.3 s · 1.4 MB

    13 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.3 s faster on a phone.

  • Render-blocking requests

    5.6 s

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

  • Reduce unused JavaScript

    3.1 s · 842 KiB

    About 842 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Reduce unused CSS

    3.1 s · 467 KiB

    About 467 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • Font display

    900 ms

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

  • Minify CSS

    600 ms · 79 KiB

    79 KiB could be saved by minifying CSS.

  • 5 third-party services on the page

    5 third-party services load with your homepage (ZenDesk, Facebook and Bootstrap CDN and others), adding 859 KiB and 575 ms of main-thread time.

  • ZenDesk adds 346 ms

    346 ms

    ZenDesk costs a phone 346 ms of main-thread work and 480 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.

  • Minify JavaScript

    300 ms · 30 KiB

    30 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 s on main-thread work while loading, 982 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 1,886 HTML elements

    The page has 1,886 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 6 long tasks on the main thread

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

  • Document request latency

    160 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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: 398 ms

    398 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 31.1 s

    31.1 s

    Your largest element takes 31.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Xylitol products”.

  • Speed Index: 16.5 s

    16.5 s

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

  • Time to Interactive: 33.1 s

    33.1 s

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

  • First Contentful Paint: 6.5 s

    6.5 s

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

  • 25 images without width and height

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

  • Total Blocking Time: 256 ms

    256 ms

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

  • Tap response (INP) held steady for real visitors

    +4%

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

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

    1.5 s

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 632 ms

    632 ms

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

  • Largest content (LCP) got 22% faster for real visitors

    -22%

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

  • Cumulative Layout Shift: 0.008

    0.008

    The layout barely moves while loading (CLS 0.008, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 9.0 MB in 191 requests

    9.0 MB

    Your homepage downloads 9.0 MB in 191 requests on a phone: images 5.9 MB (71), scripts 1.8 MB (57) and stylesheets 618 KiB (44). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    904 KiB

    3 images are downloaded at several times the size a phone draws them, for example 607b04eeb433b.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 904 KiB.

  • 21 images in older formats

    21 images (4.2 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.

  • 8 images below the first screen load straight away

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

  • About 2.6 g of CO₂ per visit

    2.56 g

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

Accessibility

7 to fixGoogle 8792
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 11 text elements with low contrast

    11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (2 elements)

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 10 links without text

    10 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 75 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 10063
  • No H1 headline

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

  • Title is short (11 characters)

    Your title is only 11 characters: “OralCare.bg”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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 (36 characters)

    Your meta description is only 36 characters: “Магазинът е създаден чрез PrestaShop”. 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.

  • No XML sitemap

    No XML sitemap at https://oralcare.bg/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 190 internal links, 2 external

    The homepage links to 190 pages on oralcare.bg and 2 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • 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://oralcare.bg/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.

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

Other pages

4 to fix58
  • 2 linked pages are broken

    Your homepage links to https://oralcare.bg/content/2-politika-na-poveritelnost and https://oralcare.bg/%D0%BC%D0%BE%D1%8F%D1%82-%D0%BF%D1%80%D0%BE%D1%84%D0%B8%D0%BB, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 3 pages share a title

    /, https://oralcare.bg/module/an_wishlist/list and https://oralcare.bg/%D0%BA%D0%BE%D0%BB%D0%B8%D1%87%D0%BA%D0%B0 all use the title “OralCare.bg”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://oralcare.bg/module/an_wishlist/list, https://oralcare.bg/5-produkti, https://oralcare.bg/6-chetki-za-zbi, https://oralcare.bg/7-pasti-za-zbi, https://oralcare.bg/8-mezhduzbni-chetki and https://oralcare.bg/9-%D0%B0%D0%BA%D1%81%D0%B5%D1%81%D0%BE%D0%B0%D1%80%D0%B8-%D0%B7%D0%B0-%D0%BC%D0%B5%D0%B6%D0%B4%D1%83%D0%B7%D1%8A%D0%B1%D0%BD%D0%B8-%D1%87%D0%B5%D1%82%D0%BA%D0%B8-%D0%B8-%D1%87%D0%B5%D1%82%D0%BA%D0%B8-%D0%B7%D0%B0-%D0%B7%D1%8A%D0%B1%D0%B8 and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://oralcare.bg/%D0%BA%D0%BE%D0%BB%D0%B8%D1%87%D0%BA%D0%B0 has no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages with very little text

    https://oralcare.bg/module/an_wishlist/list, https://oralcare.bg/6-chetki-za-zbi, https://oralcare.bg/8-mezhduzbni-chetki, https://oralcare.bg/9-%D0%B0%D0%BA%D1%81%D0%B5%D1%81%D0%BE%D0%B0%D1%80%D0%B8-%D0%B7%D0%B0-%D0%BC%D0%B5%D0%B6%D0%B4%D1%83%D0%B7%D1%8A%D0%B1%D0%BD%D0%B8-%D1%87%D0%B5%D1%82%D0%BA%D0%B8-%D0%B8-%D1%87%D0%B5%D1%82%D0%BA%D0%B8-%D0%B7%D0%B0-%D0%B7%D1%8A%D0%B1%D0%B8, https://oralcare.bg/10-konci-i-klechki-za-zbi and https://oralcare.bg/12-pri-sukhota-v-ustata and 4 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

    31 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 64 words

    The homepage has only about 64 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.

3 checks passed
  • 18 short forms

    18 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 oralcare.bg, 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 © 2021.

Stack

CMS
Powered by Creative Popup 1.6.8 - Multi-Purpose, Responsive,
E-commerce
PrestaShop
Hosting
SuperHosting.BG Ltd.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on oralcare.bg, including 19 speed issues, 7 SEO issues and 4 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

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