Website review, no card needed

rujana.bg logo

rujana.bg website review

Visit site (opens in a new tab)Reviewed 16 November 202623 issues · 62 checks

This review found 23 issues worth fixing on rujana.bg, 8 of them high impact, across 62 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
722 ms472 msMay 30Nov 14693 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026569 ms
Jun 6, 2026554 ms
Jun 13, 2026596 ms
Jun 20, 2026660 ms
Jun 27, 2026634 ms
Jul 4, 2026635 ms
Jul 11, 2026595 ms
Jul 18, 2026578 ms
Jul 25, 2026562 ms
Aug 1, 2026588 ms
Aug 8, 2026545 ms
Aug 15, 2026554 ms
Aug 22, 2026563 ms
Aug 29, 2026501 ms
Sep 5, 2026529 ms
Sep 12, 2026525 ms
Sep 19, 2026525 ms
Sep 26, 2026546 ms
Oct 3, 2026572 ms
Oct 10, 2026575 ms
Oct 17, 2026600 ms
Oct 24, 2026618 ms
Oct 31, 2026639 ms
Nov 7, 2026650 ms
Nov 14, 2026693 ms
Real-visitor tap response (INP)75th percentile, phones
122 ms64 msMay 30Oct 24115 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202675 ms
Jun 6, 202671 ms
Jun 13, 202690 ms
Jun 27, 2026106 ms
Jul 11, 2026106 ms
Jul 25, 202695 ms
Aug 1, 202695 ms
Aug 8, 202689 ms
Aug 15, 202692 ms
Aug 22, 202695 ms
Sep 5, 202691 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 2026103 ms
Oct 24, 2026115 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 rujana.bg (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rujana.bg at 0.4 s0.4 s
  2. rujana.bg at 0.8 s0.8 s
  3. rujana.bg at 1.1 s1.1 s
  4. rujana.bg at 1.5 s1.5 s
  5. rujana.bg at 1.9 s1.9 s
  6. rujana.bg at 2.3 s2.3 s
  7. rujana.bg at 2.6 s2.6 s
  8. rujana.bg at 3.0 s3.0 s

Speed

3 to fix59
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 59

    59/100

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

  • Reduce unused JavaScript

    450 ms · 209 KiB

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

  • Use efficient cache lifetimes

    200 ms · 230 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Hotjar and Google CDN and others), adding 594 KiB and 365 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 3 long tasks on the main thread

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

  • Improve image delivery

    21 KiB

    1 image could be 21 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

2 checks passed
  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 497 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

7 to fix100
  • Cumulative Layout Shift: 0.437

    0.437

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

  • Largest Contentful Paint: 5.1 s

    5.1 s

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

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

    +49%

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

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

    +20%

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

  • Time to Interactive: 7.3 s

    7.3 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 2 images without width and height

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

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: 0.7 s

    0.7 s

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

  • 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: 0.6 s

    0.6 s

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

  • Real-user TTFB: 307 ms

    307 ms

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

  • Speed Index: 2.6 s

    2.6 s

    Visually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 84 ms

    84 ms

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.40 g

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

4 checks passed
  • Page weight: 1.4 MB in 102 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 102 requests on a phone: scripts 643 KiB (29), other files 640 KiB (62) and images 70 KiB (3). That is a lean page.

  • 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

3 to fixGoogle 8795
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 image without alt text

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

  • 2 links without text

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

1 to fixGoogle 9296
  • No structured data

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

  • 26 internal links, 4 external

    The homepage links to 26 pages on rujana.bg and 4 external pages.

7 checks passed
  • Meta description: 89 characters

    Your meta description is 89 characters: “Поръчайте сладки и соленки от сладкарници „Ружана“ онлайн. Вижте нашите предложения сега!”.

  • One H1 headline

    Your main headline reads: “Сладкарници “Ружана””.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Сладкарници „Ружана“ — Русе – Сладкарници “Ружана””.

  • Canonical URL set

    The canonical URL is https://rujana.bg/.

  • 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://rujana.bg/sitemap.xml.

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.

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.

  • llms.txt published

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

Other pages

  • Your server turned our page checks away

    8 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

2 to fixGoogle 10087
  • 13 small tap targets

    13 of 19 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 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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.

  • No social proof

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

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

  • Only about 9 words

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

2 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel and Hotjar.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 1 more (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.

  • 11 cookies set on arrival

    11

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 rujana.bg, 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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

klaviyo.com · hextom.com

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
Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on rujana.bg, including 10 speed issues, 1 SEO issue and 5 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