Website review, no card needed

mojshop.rs logo

mojshop.rs website review

Visit site (opens in a new tab)Reviewed 11 November 202631 issues · 79 checks

This review found 31 issues worth fixing on mojshop.rs, 10 of them high impact, across 79 checks. The most urgent: main-thread work: 4.3 s. 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.4 s1.2 sMay 23Nov 71.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Nov 7, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
162 ms102 msMay 23Nov 7139 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026109 ms
May 30, 2026112 ms
Jun 6, 2026124 ms
Jun 13, 2026130 ms
Jun 20, 2026135 ms
Jun 27, 2026136 ms
Jul 4, 2026136 ms
Jul 11, 2026134 ms
Jul 18, 2026129 ms
Jul 25, 2026129 ms
Aug 1, 2026128 ms
Aug 8, 2026134 ms
Aug 15, 2026139 ms
Aug 22, 2026146 ms
Aug 29, 2026152 ms
Sep 5, 2026153 ms
Sep 12, 2026155 ms
Sep 19, 2026153 ms
Sep 26, 2026148 ms
Oct 3, 2026143 ms
Oct 10, 2026142 ms
Oct 17, 2026140 ms
Oct 24, 2026136 ms
Oct 31, 2026140 ms
Nov 7, 2026139 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 mojshop.rs (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix76
  • Main-thread work: 4.3 s

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

  • Mobile performance score: 76

    76/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, Clarity and beae.com and others), adding 548 KiB and 657 ms of main-thread time.

  • Improve image delivery

    450 ms · 224 KiB

    6 images could be 224 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Render-blocking requests

    550 ms

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

  • Shopify adds 271 ms

    271 ms

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

  • 1,919 HTML elements

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

  • Reduce unused JavaScript

    150 ms · 150 KiB

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

  • 9 long tasks on the main thread

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

  • Minify JavaScript

    50 ms · 13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    22 KiB

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

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

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

    8 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 5.2 s

    5.2 s

    Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Radovi u bašti”.

  • Time to Interactive: 9.0 s

    9.0 s

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

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

    +26%

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

  • Total Blocking Time: 233 ms

    233 ms

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

  • Speed Index: 3.4 s

    3.4 s

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

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

    +12%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.4 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.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: 115 ms

    115 ms

    Real visitors wait 115 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 309 ms

    309 ms

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

  • 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

    0

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

Images and page weight

2 to fix81
  • Page weight: 2.1 MB in 308 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 308 requests on a phone: other files 1,000 KiB (166), scripts 579 KiB (98) and images 432 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    radovi-u-basti.jpg 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).

  • 3 images in older formats

    3 images (298 KiB) 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.

  • About 0.6 g of CO₂ per visit

    0.61 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8292
  • 2 buttons without a name

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should 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 (2 elements)

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

  • 11 links without text

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

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

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

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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

3 to fixGoogle 9288
  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("mojshop.rs")”.

  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 438 internal links, 5 external

    The homepage links to 438 pages on mojshop.rs and 5 external pages.

5 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Internet prodavnica za domaćine, majstore, poljoprivrednike, vikendaše i baštovane. Opremi kuću, uredi okućnicu! Poruči…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Mojshop.rs | Online prodaja alata, delova, opreme i zaštite”.

  • Canonical URL set

    The canonical URL is https://mojshop.rs/.

  • 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://mojshop.rs/sitemap.xml.

AI search readiness

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 8 pages without a meta description

    https://mojshop.rs/collections/saksije-i-zardinjere, https://mojshop.rs/collections/drzaci-saksija, https://mojshop.rs/collections/vestacka-ziva-ograda, https://mojshop.rs/collections/ogradice-za-baste, https://mojshop.rs/collections/granicnik-za-travu and https://mojshop.rs/collections/kapije-i-paneli and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97138616&tm=shpfy_ui&Ver=2&mid=7d12ef97-ed6a-43c0-8193-5e0bf9f80d7f&bo=1&sid=2c6287b0dd6811f189d01323cf1bbf40&vid=2c62a8e0dd6811f1875dc98b0c4bf332&vids=1&msclkid=N&pi=.

  • 4 small tap targets

    4 of 11 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 “Unsupported locale: "sr"”.

1 checks passed
  • 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 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 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 314 words of copy

    The homepage carries about 314 words of visible text.

3 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 mojshop.rs, 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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · Judge Me Reviews · Seo Manager Venntov · makeprosimp.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

  • The footer still says © 2013.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on mojshop.rs, including 12 speed issues, 3 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