Website review, no card needed

bogas.ro logo

bogas.ro website review

Visit site (opens in a new tab)Reviewed 8 November 202626 issues · 79 checks

This review found 26 issues worth fixing on bogas.ro, 7 of them high impact, across 79 checks. The most urgent: avoid multiple page redirects. 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
1.3 s952 msMay 16Oct 311.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 2026996 ms
Oct 24, 2026987 ms
Oct 31, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
142 ms89 msMay 16Oct 31102 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026124 ms
May 23, 2026124 ms
May 30, 2026126 ms
Jun 6, 2026129 ms
Jun 13, 2026130 ms
Jun 20, 2026134 ms
Jun 27, 2026136 ms
Jul 4, 2026130 ms
Jul 11, 2026120 ms
Jul 18, 2026116 ms
Jul 25, 2026112 ms
Aug 1, 2026110 ms
Aug 8, 2026106 ms
Aug 15, 2026103 ms
Aug 22, 202696 ms
Aug 29, 202695 ms
Sep 5, 202696 ms
Sep 12, 202697 ms
Sep 19, 2026102 ms
Sep 26, 2026103 ms
Oct 3, 2026102 ms
Oct 10, 2026102 ms
Oct 17, 202699 ms
Oct 24, 202698 ms
Oct 31, 2026102 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 bogas.ro (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bogas.ro at 0.9 s0.9 s
  2. bogas.ro at 1.7 s1.7 s
  3. bogas.ro at 2.6 s2.6 s
  4. bogas.ro at 3.5 s3.5 s
  5. bogas.ro at 4.3 s4.3 s
  6. bogas.ro at 5.2 s5.2 s
  7. bogas.ro at 6.1 s6.1 s
  8. bogas.ro at 6.9 s6.9 s

Speed

8 to fix75
  • Avoid multiple page redirects

    1.8 s

    The page goes through 1 redirect before it starts loading, costing about 1.8 s. Link and advertise the final URL directly.

  • 7,853 HTML elements

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

  • Main-thread work: 4.0 s

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

  • Mobile performance score: 75

    75/100

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

  • Render-blocking requests

    750 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Facebook and Klaviyo and others), adding 1.1 MB and 463 ms of main-thread time.

  • Shopify adds 256 ms

    256 ms

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

  • Use efficient cache lifetimes

    255 KiB

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

  • Reduce unused JavaScript

    150 ms · 98 KiB

    About 98 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 26 KiB

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

  • Improve image delivery

    172 KiB

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

  • 3 long tasks on the main thread

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

  • Duplicated JavaScript

    43 KiB

    43 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    31 KiB

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

    11 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 6.2 s

    6.2 s

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

  • Time to Interactive: 12.7 s

    12.7 s

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

  • Speed Index: 4.7 s

    4.7 s

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

10 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.4 s

    1.4 s

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

  • Real-user INP: 152 ms

    152 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 318 ms

    318 ms

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

  • Tap response (INP) got 19% faster for real visitors

    -19%

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 18 ms

    18 ms

    Scripts block the page for only 18 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix69
  • Page weight: 3.0 MB in 328 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 328 requests on a phone: scripts 1.0 MB (141), other files 930 KiB (142) and images 744 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    IMG_5689.png 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).

  • 1 image far larger than shown

    139 KiB

    1 image is downloaded at several times the size a phone draws it, for example 1793808898278-3205330-BlackFridaySaleLabel_e3a0d855-31d7-440 at 1,864 px wide, shown at 43 px. Resized copies would save about 139 KiB.

  • About 0.9 g of CO₂ per visit

    0.85 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 102.5 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

4 to fixGoogle 9395
  • 259 text elements with low contrast

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

  • 20 links without text

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

  • 4 form fields without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 204 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

Google 92100
  • 521 internal links, 22 external

    The homepage links to 521 pages on bogas.ro and 22 external pages.

8 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Bogas, brand românesc de îmbrăcăminte pentru femei din 2012: rochii, compleuri, geci și hanorace. Descoperă colecția de…”.

  • One H1 headline

    Your main headline reads: “Bogas, îmbrăcăminte pentru femei”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “Bogas · Îmbrăcăminte pentru femei online”.

  • Canonical URL set

    The canonical URL is https://www.bogas.ro/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://www.bogas.ro/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (2,134 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix83
  • 2 linked pages hidden from search

    https://www.bogas.ro/pages/vazute-recent and https://www.bogas.ro/pages/favorite are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.bogas.ro/pages/vazute-recent and https://www.bogas.ro/pages/favorite have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.bogas.ro/collections/reduceri and https://www.bogas.ro/collections/bogas-nav-cele-mai-cumparate 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 193 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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 ()”.

2 checks passed
  • Tap targets are thumb-sized

    45 of 47 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,868 words of copy

    The homepage carries about 1,868 words of visible text.

  • Urgency cues

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

4 checks passed
  • 24 calls to action

    The homepage has 24 calls to action, for example “Shop all dresses”, “Shop all” and “Shop All”.

  • 47 short forms

    47 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and TikTok Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 13 cookies set on arrival

    13

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

  • 21 other companies contacted

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

Apps on your store

Your storefront loads 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Themarketer · Ta Labels Badges · Klaviyo Email Marketing Sms · T Lab Ai Translate · Gdpr Cookie Consent

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on bogas.ro, including 11 speed 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