Website review, no card needed

zipnorth.com logo

zipnorth.com website review

Visit site (opens in a new tab)Reviewed 8 November 202621 issues · 81 checks

This review found 21 issues worth fixing on zipnorth.com, 4 of them high impact, across 81 checks. The most urgent: 1 text element with low contrast. 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.6 s1.1 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.4 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.3 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
80 ms70 msMay 16Oct 3171 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202677 ms
May 23, 202676 ms
May 30, 202677 ms
Jun 6, 202677 ms
Jun 13, 202672 ms
Jun 20, 202672 ms
Jun 27, 202672 ms
Jul 4, 202672 ms
Jul 11, 202672 ms
Jul 18, 202678 ms
Jul 25, 202679 ms
Aug 1, 202679 ms
Aug 8, 202676 ms
Aug 15, 202673 ms
Aug 22, 202677 ms
Aug 29, 202677 ms
Sep 5, 202677 ms
Sep 12, 202678 ms
Sep 19, 202678 ms
Oct 3, 202678 ms
Oct 10, 202678 ms
Oct 17, 202678 ms
Oct 24, 202675 ms
Oct 31, 202671 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 zipnorth.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix74
  • Improve image delivery

    850 ms · 317 KiB

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

  • Mobile performance score: 74

    74/100

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

  • Render-blocking requests

    650 ms

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

  • 2,226 HTML elements

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, qikify.com and logbase.io and others), adding 506 KiB and 204 ms of main-thread time.

  • 1 long task on the main thread

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

  • Reduce unused JavaScript

    60 KiB

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

  • Reduce unused CSS

    23 KiB

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

  • Use efficient cache lifetimes

    7 KiB

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

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 32 ms

    32 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 5.7 s

    5.7 s

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

  • Time to Interactive: 7.4 s

    7.4 s

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

  • Speed Index: 4.1 s

    4.1 s

    Visually, the page fills in at 4.1 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-10-31, real Chrome visitors' tap response (inp) went from 77 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    1.3 s

    Real visitors wait 1.3 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.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: 478 ms

    478 ms

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • Cumulative Layout Shift: 0.092

    0.092

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Total Blocking Time: 5 ms

    5 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.6 MB in 233 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 233 requests on a phone: images 955 KiB (25), other files 859 KiB (95) and scripts 673 KiB (77). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (24 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.75 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • Meta description is long (168 characters)

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 52 internal links, 10 external

    The homepage links to 52 pages on zipnorth.com and 10 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Zip North”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “Zip North Kart Components & Racewear”.

  • Canonical URL set

    The canonical URL is https://zipnorth.com/.

  • Structured data in place

    Structured data found: Organization 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://zipnorth.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: 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,896 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://zipnorth.com/collections/data-logging-timing and https://zipnorth.com/collections/kart-tools-maintenance have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://zipnorth.com/collections/kart-engines-parts, https://zipnorth.com/collections/data-logging-timing, https://zipnorth.com/collections/tyres, https://zipnorth.com/collections/kart-republic-copy, https://zipnorth.com/collections/cadet-inter and https://zipnorth.com/collections/karts-parts-general-spares and 3 others 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 (of 22 found) and read each the way a search engine does.

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

  • 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix80
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • Only about 249 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NEW PRODUCTS HERE” and “SHOP DATA LOGGING & TIMING”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Join”, “Shop New Products here” and “Shop Data Logging & Timing”.

  • 5 short forms

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

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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

  • 7 cookies set on arrival

    7

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

  • 9 other companies contacted

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

Apps your storefront loads

Dual Price Display Pro · Selleasy · Smart Menu · Checkout Rules

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on zipnorth.com, including 7 speed issues, 2 SEO issues and 4 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