Website review, no card needed

dobreva.com logo

dobreva.com website review

Visit site (opens in a new tab)Reviewed 16 November 202646 issues · 87 checks

This review found 46 issues worth fixing on dobreva.com, 16 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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.5 s2.1 sMay 30Nov 142.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Nov 7, 20262.3 s
Nov 14, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
193 ms131 msMay 30Nov 14167 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026138 ms
Jun 6, 2026150 ms
Jun 13, 2026150 ms
Jun 20, 2026148 ms
Jun 27, 2026143 ms
Jul 4, 2026143 ms
Jul 11, 2026145 ms
Jul 18, 2026152 ms
Jul 25, 2026154 ms
Aug 1, 2026159 ms
Aug 8, 2026162 ms
Aug 15, 2026171 ms
Aug 22, 2026177 ms
Aug 29, 2026176 ms
Sep 5, 2026167 ms
Sep 12, 2026162 ms
Sep 19, 2026162 ms
Sep 26, 2026169 ms
Oct 3, 2026174 ms
Oct 10, 2026179 ms
Oct 17, 2026186 ms
Oct 24, 2026168 ms
Oct 31, 2026163 ms
Nov 7, 2026164 ms
Nov 14, 2026167 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 dobreva.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dobreva.com at 0.6 s0.6 s
  2. dobreva.com at 1.2 s1.2 s
  3. dobreva.com at 1.8 s1.8 s
  4. dobreva.com at 2.5 s2.5 s
  5. dobreva.com at 3.1 s3.1 s
  6. dobreva.com at 3.7 s3.7 s
  7. dobreva.com at 4.3 s4.3 s
  8. dobreva.com at 4.9 s4.9 s

Speed

14 to fix44
  • Reduce unused JavaScript

    2.1 s · 977 KiB

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

  • Mobile performance score: 44

    44/100

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

  • Main-thread work: 5.4 s

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

  • 3,726 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Hotjar, Google Tag Manager and Shopify and others), adding 1.2 MB and 1.6 s of main-thread time.

  • Use efficient cache lifetimes

    600 ms · 267 KiB

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

  • 14 long tasks on the main thread

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

  • Hotjar adds 548 ms

    548 ms

    Hotjar costs a phone 548 ms of main-thread work and 65 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.

  • Render-blocking requests

    450 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Google Tag Manager adds 401 ms

    401 ms

    Google Tag Manager costs a phone 401 ms of main-thread work and 316 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.

  • Reduce unused CSS

    300 ms · 61 KiB

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

  • Minify JavaScript

    300 ms · 59 KiB

    59 KiB could be saved by minifying JavaScript.

  • Shopify adds 315 ms

    315 ms

    Shopify costs a phone 315 ms of main-thread work and 417 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.

  • Improve image delivery

    300 ms · 15 KiB

    1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Font display

    50 ms

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

  • 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: 18 ms

    18 ms

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

Core Web Vitals

8 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: 11.7 s

    11.7 s

    Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 15.1 s

    15.1 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Tap response (INP) got 15% slower for real visitors

    +15%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

4 checks passed
  • Real-user INP: 120 ms

    120 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.011

    0.011

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

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 243 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 243 requests on a phone: scripts 1.2 MB (57), other files 909 KiB (102) and images 702 KiB (63). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.89 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 7988
  • 3 buttons without a name

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

  • 16 tap targets too small

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

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

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

  • ARIA toggle fields must have an accessible name (1 element)

    ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 2 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 8584
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Best Sellers”). One clear main headline is easier for people and search engines.

  • Meta description is long (187 characters)

    Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.

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

  • 96 internal links, 5 external

    The homepage links to 96 pages on dobreva.com and 5 external pages.

5 checks passed
  • Title: 35 characters

    Your title is a healthy 35 characters: “Pretty, Comfy and Sexy Bras丨Dobreva”.

  • Canonical URL set

    The canonical URL is https://dobreva.com/.

  • 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://dobreva.com/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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,125 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://dobreva.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix71
  • 1 page points its canonical at the homepage

    https://dobreva.com/discount/DOB10 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://dobreva.com/discount/DOB10 all use the title “Pretty, Comfy and Sexy Bras丨Dobreva”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://dobreva.com/collections/new-in, https://dobreva.com/collections/best-sellers, https://dobreva.com/collections/bras, https://dobreva.com/collections/new-in-bras and https://dobreva.com/collections/mesh-bra have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://dobreva.com/discount/DOB10 and https://dobreva.com/collections use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://dobreva.com/collections/bras and https://dobreva.com/collections/lace-bra 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 32 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.

  • 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 9687
  • 100 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

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

  • 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 388 words of copy

    The homepage carries about 388 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 Now”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “SHOP ALL”, “SHOP BY STYLES” and “Shop Now”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 16 cookies set on arrival

    16

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

  • 24 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on dobreva.com, including 22 speed issues, 4 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

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