Website review, no card needed

offnorth.com logo

offnorth.com website review

Visit site (opens in a new tab)Reviewed 20 November 202631 issues · 82 checks

This review found 31 issues worth fixing on offnorth.com, 9 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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
2.1 s1.4 sMay 30Nov 142.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.8 s
Nov 7, 20262.0 s
Nov 14, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
331 ms168 msMay 30Nov 14312 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026277 ms
Jun 6, 2026281 ms
Jun 13, 2026271 ms
Jun 20, 2026255 ms
Jun 27, 2026257 ms
Jul 4, 2026255 ms
Jul 11, 2026259 ms
Jul 18, 2026265 ms
Jul 25, 2026261 ms
Aug 1, 2026267 ms
Aug 8, 2026245 ms
Aug 15, 2026219 ms
Aug 22, 2026208 ms
Aug 29, 2026187 ms
Sep 5, 2026187 ms
Sep 12, 2026197 ms
Sep 19, 2026204 ms
Sep 26, 2026212 ms
Oct 3, 2026221 ms
Oct 10, 2026230 ms
Oct 17, 2026246 ms
Oct 24, 2026262 ms
Oct 31, 2026287 ms
Nov 7, 2026307 ms
Nov 14, 2026312 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 offnorth.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. offnorth.com at 2.1 s2.1 s
  2. offnorth.com at 4.1 s4.1 s
  3. offnorth.com at 6.2 s6.2 s
  4. offnorth.com at 8.2 s8.2 s
  5. offnorth.com at 10.3 s10.3 s
  6. offnorth.com at 12.3 s12.3 s
  7. offnorth.com at 14.4 s14.4 s
  8. offnorth.com at 16.4 s16.4 s

Speed

13 to fix51
  • Use efficient cache lifetimes

    3.5 s · 559 KiB

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

  • Reduce unused JavaScript

    1.8 s · 365 KiB

    About 365 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Main-thread work: 6.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (shiprocket.in, Facebook and omnisnippet1.com and others), adding 1.7 MB and 1.8 s of main-thread time.

  • Mobile performance score: 51

    51/100

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

  • Render-blocking requests

    750 ms

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

  • shiprocket.in adds 555 ms

    555 ms

    shiprocket.in costs a phone 555 ms of main-thread work and 120 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.

  • Reduce unused CSS

    300 ms · 40 KiB

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

  • Facebook adds 293 ms

    293 ms

    Facebook costs a phone 293 ms of main-thread work and 263 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.

  • omnisnippet1.com adds 273 ms

    273 ms

    omnisnippet1.com costs a phone 273 ms of main-thread work and 94 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.

  • zohocdn.com adds 271 ms

    271 ms

    zohocdn.com costs a phone 271 ms of main-thread work and 82 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.

  • 11 long tasks on the main thread

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

  • Shopify adds 137 ms

    137 ms

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

  • Improve image delivery

    162 KiB

    10 images could be 162 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    20 KiB

    20 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

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

    9 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 12.9 s

    12.9 s

    Your largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Man in a tawny port Supima interlock polo”.

  • Time to Interactive: 14.5 s

    14.5 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user TTFB: 951 ms

    951 ms

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

  • Total Blocking Time: 401 ms

    401 ms

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

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

    +11%

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

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

    +11%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 178 ms

    178 ms

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

    1.7 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 3.7 MB in 483 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 483 requests on a phone: scripts 1.3 MB (163), other files 1.2 MB (268) and images 769 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    21 KiB

    1 image is downloaded at several times the size a phone draws it, for example offnorth-home-tile-hoodie.jpg at 500 px wide, shown at 136 px. Resized copies would save about 21 KiB.

  • 1 image in older formats

    1 image (64 KiB) 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 1.0 g of CO₂ per visit

    1.04 g

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

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

2 to fixGoogle 9797
  • 2 text elements with low contrast

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

  • 21 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 10085
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Supima Cotton T-Shirts & Polos in India, Made in Tirupur | Offnorth”.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Offnorth Fashions”, “The Supima Polo” and “The world's finest cotton.Our softest polo.”). 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.

  • 129 internal links, 3 external

    The homepage links to 129 pages on offnorth.com and 3 external pages.

5 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Shop 100% Supima cotton t-shirts, polos and winterwear made in Tirupur. Softer, stronger and fade-resistant. Free deliv…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage, OnlineStore and Organization.

  • 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://offnorth.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (1,366 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://offnorth.com/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 34 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 7 third-party cookies

    7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 468 words of copy

    The homepage carries about 468 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now · ₹1,999”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Exclusive Interlock Polo (Must Try)”, “Single Jersey Polo (Must Try)” and “Supima Lycra Crew (Must Try)”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: a star rating and “Loved by 25K+ customers”.

  • Analytics in place

    Analytics detected: Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email 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

1 to fix
  • 4 trackers load before any consent

    4

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

  • 31 cookies set on arrival

    31

    Opening the homepage sets 31 cookies, 4 of them by other companies (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.

  • 34 other companies contacted

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

Apps your storefront loads

Omnisend · Ecomsend · zoho.in · shiprocket.in · nitrocommerce.ai · hillteck.com · pagesense.io · offnorth.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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Gurugram

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 offnorth.com, including 20 speed issues and 3 SEO issues. 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