Website review, no card needed

veshte.hr logo

veshte.hr website review

Visit site (opens in a new tab)Reviewed 16 November 202633 issues · 83 checks

This review found 33 issues worth fixing on veshte.hr, 10 of them high impact, across 83 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
1.7 s1.2 sMay 30Nov 141.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.3 s
Jun 20, 20261.2 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.5 s
Jul 18, 20261.6 s
Jul 25, 20261.5 s
Aug 1, 20261.3 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.5 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Nov 7, 20261.4 s
Nov 14, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
153 ms75 msMay 30Nov 14105 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026110 ms
Jun 6, 2026114 ms
Jun 13, 2026113 ms
Jun 20, 2026111 ms
Jun 27, 2026105 ms
Jul 4, 2026100 ms
Jul 11, 2026102 ms
Jul 18, 202699 ms
Jul 25, 202698 ms
Aug 1, 202695 ms
Aug 8, 202687 ms
Aug 15, 202684 ms
Aug 22, 202696 ms
Aug 29, 2026102 ms
Sep 5, 2026107 ms
Sep 12, 2026120 ms
Sep 19, 2026122 ms
Sep 26, 2026144 ms
Oct 3, 2026128 ms
Oct 10, 2026128 ms
Oct 17, 2026112 ms
Oct 24, 2026105 ms
Oct 31, 2026106 ms
Nov 7, 2026101 ms
Nov 14, 2026105 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 veshte.hr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. veshte.hr at 0.8 s0.8 s
  2. veshte.hr at 1.7 s1.7 s
  3. veshte.hr at 2.5 s2.5 s
  4. veshte.hr at 3.4 s3.4 s
  5. veshte.hr at 4.2 s4.2 s
  6. veshte.hr at 5.0 s5.0 s
  7. veshte.hr at 5.9 s5.9 s
  8. veshte.hr at 6.7 s6.7 s

Speed

8 to fix79
  • Render-blocking requests

    1.0 s

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

  • Main-thread work: 4.5 s

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

  • Improve image delivery

    150 ms · 1.2 MB

    42 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Mobile performance score: 79

    79/100

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 587 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    300 ms · 54 KiB

    About 54 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.

  • Shopify adds 212 ms

    212 ms

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

  • 2,102 HTML elements

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and shop.app), adding 741 KiB and 235 ms of main-thread time.

  • Reduce unused JavaScript

    143 KiB

    About 143 KiB of JavaScript is downloaded but never used on this page.

  • Minify JavaScript

    16 KiB

    16 KiB could be saved by minifying JavaScript.

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

  • Use efficient cache lifetimes

    1 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 3.9 s

    3.9 s

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

  • Time to Interactive: 7.1 s

    7.1 s

    The page becomes fully interactive after 7.1 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.

  • Total Blocking Time: 269 ms

    269 ms

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -8%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

8 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.9 s

    1.9 s

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

  • Real-user INP: 124 ms

    124 ms

    Real visitors wait 124 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.0 s

    1.0 s

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

  • Real-user TTFB: 439 ms

    439 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

3 to fix53
  • Page weight: 5.1 MB in 350 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 350 requests on a phone: images 3.1 MB (67), scripts 829 KiB (157) and other files 716 KiB (95). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    veshte_banner-4_2000x.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).

  • 4 images far larger than shown

    452 KiB

    4 images are downloaded at several times the size a phone draws them, for example veshte_banner-4_2000x.png at 1,800 px wide, shown at 390 px. Resized copies would save about 452 KiB.

  • About 1.4 g of CO₂ per visit

    1.44 g

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

5 to fixGoogle 8692
  • 23 text elements with low contrast

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

  • ARIA commands must have an accessible name (22 elements)

    ARIA commands must have an accessible name: 22 elements on the page fail this check, rated serious by axe-core.

  • 7 tap targets too small

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 84 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9281
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • 2 H1 headlines

    There are 2 <h1> headlines (“NAŠA PREPORUKA” and “NAŠA PREPORUKA”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 58 internal links, 10 external

    The homepage links to 58 pages on veshte.hr and 10 external pages.

5 checks passed
  • Title: 33 characters

    Your title is a healthy 33 characters: “VESHTE - svečane haljine — Veshte”.

  • Canonical URL set

    The canonical URL is https://veshte.hr/.

  • Structured data in place

    Structured data found: WebSite.

  • 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://veshte.hr/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 (903 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix69
  • 1 linked page is broken

    Your homepage links to https://veshte.hr/collections/vendors, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 3 pages without a meta description

    https://veshte.hr/collections/all, https://veshte.hr/collections and https://veshte.hr/collections/hrvatski-dizajneri have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://veshte.hr/products/baloner-cles-amiee-chocolate and https://veshte.hr/products/baloner-cles-amiee-beige use the same meta description. A description written for each page earns more clicks.

  • 2 pages with very little text

    https://veshte.hr/pages/contact and https://veshte.hr/collections 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 17 found) and read each the way a search engine does.

5 checks passed
  • 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 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'dataset')”.

2 checks passed
  • Tap targets are thumb-sized

    61 of 76 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 411 words of visible text.

  • Urgency cues

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

2 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Quick shop”, “Shop collection” and “Sign up”.

  • 5 short forms

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

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 6 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 veshte.hr, 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

Inbox · Unidigital Sidrena Cijena

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

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on veshte.hr, including 13 speed issues, 4 SEO issues and 3 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