Website review, no card needed

mrakovic.com logo

mrakovic.com website review

Visit site (opens in a new tab)Reviewed 21 November 202629 issues · 78 checks

This review found 29 issues worth fixing on mrakovic.com, 5 of them high impact, across 78 checks. The most urgent: scrollable region must have keyboard access (1 element). 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.1 s869 msMay 30Nov 14907 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.0 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.0 s
Jun 27, 20261.1 s
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 2026957 ms
Aug 29, 2026896 ms
Sep 5, 2026939 ms
Sep 12, 2026937 ms
Sep 19, 2026990 ms
Sep 26, 20261.1 s
Oct 3, 20261.0 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 2026986 ms
Oct 31, 2026966 ms
Nov 7, 2026959 ms
Nov 14, 2026907 ms
Real-visitor tap response (INP)75th percentile, phones
109 ms84 msMay 30Nov 1497 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202693 ms
Jun 6, 202697 ms
Jun 13, 202696 ms
Jun 20, 202696 ms
Jun 27, 202694 ms
Jul 4, 202689 ms
Jul 11, 202688 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202690 ms
Aug 8, 202695 ms
Aug 15, 202696 ms
Aug 22, 202698 ms
Aug 29, 202698 ms
Sep 5, 2026103 ms
Sep 12, 2026103 ms
Sep 19, 2026103 ms
Sep 26, 2026104 ms
Oct 3, 2026101 ms
Oct 10, 2026102 ms
Oct 17, 2026106 ms
Oct 24, 2026103 ms
Oct 31, 2026104 ms
Nov 7, 2026103 ms
Nov 14, 202697 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 mrakovic.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mrakovic.com at 0.5 s0.5 s
  2. mrakovic.com at 0.9 s0.9 s
  3. mrakovic.com at 1.4 s1.4 s
  4. mrakovic.com at 1.8 s1.8 s
  5. mrakovic.com at 2.3 s2.3 s
  6. mrakovic.com at 2.7 s2.7 s
  7. mrakovic.com at 3.2 s3.2 s
  8. mrakovic.com at 3.6 s3.6 s

Speed

6 to fix64
  • Improve image delivery

    350 ms · 988 KiB

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

  • Mobile performance score: 64

    64/100

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

  • Render-blocking requests

    450 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, minmaxify.com and Shopify and others), adding 1.4 MB and 267 ms of main-thread time.

  • Reduce unused JavaScript

    300 ms · 74 KiB

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

  • Shopify adds 29 ms

    29 ms

    Shopify costs a phone 29 ms of main-thread work and 1.1 MB 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

    150 ms · 21 KiB

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

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    15 KiB

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

2 checks passed
  • Main-thread work: 1.3 s

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

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

    10.2 s

    Your largest element takes 10.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: 10.5 s

    10.5 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • 43 images without width and height

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

  • Speed Index: 5.3 s

    5.3 s

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 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: 111 ms

    111 ms

    Real visitors wait 111 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.1 s

    1.1 s

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

  • Real-user TTFB: 445 ms

    445 ms

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

  • Total Blocking Time: 98 ms

    98 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix69
  • Page weight: 2.8 MB in 217 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 217 requests on a phone: images 1.5 MB (41), other files 778 KiB (97) and scripts 417 KiB (42). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    WhatsApp_Image_2025-03-25_at_10.45.02_AM.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).

  • 4 images far larger than shown

    96 KiB

    4 images are downloaded at several times the size a phone draws them, for example 17_b11d3cd9-a51f-4a93-b851-f39e57cc28d1.png at 1,152 px wide, shown at 360 px. Resized copies would save about 96 KiB.

  • About 0.8 g of CO₂ per visit

    0.79 g

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

3 to fixGoogle 9295
  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 15 images without alt text

    15 images have no alt text, which hurts accessibility and image search.

  • 3 links without text

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

1 checks passed
  • 51 automated accessibility rules passed

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

4 to fixGoogle 8581
  • Title is short (19 characters)

    Your title is only 19 characters: “Mrakovic Fine Foods”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (30 characters)

    Your meta description is only 30 characters: “Welcome to Mrakovic Fine Foods”. 70 to 160 characters is enough to sell the click.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • One H1 headline

    Your <h1> is empty.

  • 36 internal links, 20 external

    The homepage links to 36 pages on mrakovic.com and 20 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.mrakovic.com/.

  • Structured data in place

    Structured data found: Organization, Restaurant 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.mrakovic.com/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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 8 pages without a meta description

    https://www.mrakovic.com/collections/all, https://www.mrakovic.com/policies/shipping-policy, https://www.mrakovic.com/pages/catering, https://www.mrakovic.com/pages/where-to-find-our-products, https://www.mrakovic.com/pages/recipe and https://www.mrakovic.com/pages/walmart and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.mrakovic.com/pages/catering, https://www.mrakovic.com/pages/where-to-find-our-products, https://www.mrakovic.com/pages/walmart, https://www.mrakovic.com/pages/campaign, https://www.mrakovic.com/pages/contact-us and https://www.mrakovic.com/pages/blog 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 and read each the way a search engine does.

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

  • 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 9291
  • 6 JavaScript errors while loading

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

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix85
  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 155 words

    The homepage has only about 155 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Order your Mrakovic favourites online” and “SHOP LOCAL”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “SHOP LOCAL”, “Shop Now” and “Order your Mrakovic favourites online”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 10 cookies set on arrival

    10

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 mrakovic.com, 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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Minmaxify Order Limits · nfcube.com · addons.business

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

CMS
WordPress
Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Company

Headquarters
Toronto

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on mrakovic.com, including 11 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