Website review, no card needed

marnicsmobile.ca logo

marnicsmobile.ca website review

Visit site (opens in a new tab)Reviewed 13 November 202620 issues · 67 checks

This review found 20 issues worth fixing on marnicsmobile.ca, 6 of them high impact, across 67 checks. The most urgent: fails Core Web Vitals for real visitors. 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
838 ms675 msMay 23Nov 7739 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026741 ms
May 30, 2026766 ms
Jun 6, 2026737 ms
Jun 13, 2026733 ms
Jun 20, 2026795 ms
Jun 27, 2026772 ms
Jul 4, 2026808 ms
Jul 11, 2026819 ms
Jul 18, 2026723 ms
Jul 25, 2026726 ms
Aug 1, 2026714 ms
Aug 8, 2026694 ms
Aug 15, 2026727 ms
Aug 22, 2026743 ms
Aug 29, 2026743 ms
Sep 5, 2026775 ms
Sep 12, 2026762 ms
Sep 19, 2026743 ms
Sep 26, 2026737 ms
Oct 3, 2026711 ms
Oct 10, 2026717 ms
Oct 17, 2026739 ms
Oct 24, 2026781 ms
Oct 31, 2026765 ms
Nov 7, 2026739 ms
Real-visitor tap response (INP)75th percentile, phones
183 ms115 msMay 23Nov 7136 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026146 ms
May 30, 2026144 ms
Jun 6, 2026130 ms
Jun 13, 2026146 ms
Jun 20, 2026162 ms
Jun 27, 2026147 ms
Jul 4, 2026154 ms
Jul 11, 2026146 ms
Jul 18, 2026129 ms
Jul 25, 2026125 ms
Aug 1, 2026124 ms
Aug 8, 2026123 ms
Aug 15, 2026129 ms
Aug 22, 2026144 ms
Aug 29, 2026140 ms
Sep 5, 2026146 ms
Sep 12, 2026147 ms
Sep 19, 2026145 ms
Sep 26, 2026157 ms
Oct 3, 2026164 ms
Oct 10, 2026175 ms
Oct 17, 2026175 ms
Oct 24, 2026172 ms
Oct 31, 2026156 ms
Nov 7, 2026136 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 marnicsmobile.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix100
  • Render-blocking requests

    700 ms

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

  • 1,926 HTML elements

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

  • Use efficient cache lifetimes

    108 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, ds-cdn.com and setubridgeapps.com and others), adding 335 KiB and 3 ms of main-thread time.

  • Reduce unused CSS

    26 KiB

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

  • Improve image delivery

    10 KiB

    2 images could be 10 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.

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.2 s

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

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

2 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user CLS: 0.20

    0.20

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

10 checks passed
  • Real-user LCP: 0.9 s

    0.9 s

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

  • Real-user INP: 130 ms

    130 ms

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

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 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.

  • 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

    0

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

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.

  • Speed Index: 1.4 s

    1.4 s

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

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.1 s

    1.1 s

    The page is fully interactive after 1.1 s.

Images and page weight

2 to fix75
  • 1 image over 500 KB

    element_picker.gif weighs 1.4 MB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (1.4 MB) is 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.2 g of CO₂ per visit

    0.16 g

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

3 checks passed
  • Page weight: 565 KiB in 32 requests

    565 KiB

    Your homepage downloads 565 KiB in 32 requests on a phone: scripts 433 KiB (23), HTML 68 KiB (1) and stylesheets 36 KiB (2). That is a lean page.

  • 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

5 to fixGoogle 9193
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 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 (6 elements)

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

  • 6 form fields without a label

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

  • 1 link without text

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

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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 10080
  • Title is short (14 characters)

    Your title is only 14 characters: “Marnics Mobile”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (313 characters)

    Your meta description is 313 characters; Google truncates after about 160, so the end of your pitch is cut.

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

  • 217 internal links, 11 external

    The homepage links to 217 pages on marnicsmobile.ca and 11 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://marnicsmobile.ca/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and 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://marnicsmobile.ca/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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0259/8135/4043/files/file.png?v=1638521783.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    103 of 107 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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 1,409 words of copy

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

4 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “Contact Us”, “Get a Repair Estimate” and “Get a Trade in Estimate”.

  • 19 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 5 cookies set on arrival

    5

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 marnicsmobile.ca, 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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Preorder Now Pre Order Pq · Reamaze Live Chat Helpdesk · Hulk Contact Form Builder · Preorder Manager Prequik · elfsight.com · hulkapps.com · powr.io · hextom.com · bookthatapp.com · kxcdn.com · digitaloceanspaces.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
Google 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 20 issues on marnicsmobile.ca, including 4 speed issues, 4 SEO 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