Website review, no card needed

arcticleaf.com logo

arcticleaf.com website review

Visit site (opens in a new tab)Reviewed 21 October 202622 issues · 72 checks

This review found 22 issues worth fixing on arcticleaf.com, 7 of them high impact, across 72 checks. The most urgent: reduce unused JavaScript. 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
3.7 s1.8 sMay 23Sep 192.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.2 s
May 30, 20262.0 s
Jun 6, 20262.1 s
Jun 13, 20262.3 s
Jun 20, 20262.7 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.4 s
Aug 8, 20262.7 s
Aug 15, 20262.9 s
Aug 22, 20263.1 s
Aug 29, 20262.9 s
Sep 5, 20263.2 s
Sep 12, 20262.8 s
Sep 19, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
356 ms173 msMay 30Aug 22322 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026194 ms
Jun 6, 2026225 ms
Jun 13, 2026194 ms
Jun 20, 2026265 ms
Jun 27, 2026310 ms
Jul 4, 2026290 ms
Jul 11, 2026307 ms
Jul 18, 2026308 ms
Jul 25, 2026300 ms
Aug 1, 2026335 ms
Aug 8, 2026326 ms
Aug 15, 2026297 ms
Aug 22, 2026322 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 arcticleaf.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. arcticleaf.com at 0.5 s0.5 s
  2. arcticleaf.com at 1.0 s1.0 s
  3. arcticleaf.com at 1.4 s1.4 s
  4. arcticleaf.com at 1.9 s1.9 s
  5. arcticleaf.com at 2.4 s2.4 s
  6. arcticleaf.com at 2.9 s2.9 s
  7. arcticleaf.com at 3.3 s3.3 s
  8. arcticleaf.com at 3.8 s3.8 s

Speed

7 to fix65
  • Reduce unused JavaScript

    1.6 s · 419 KiB

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

  • Use efficient cache lifetimes

    1.2 s · 330 KiB

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

  • Main-thread work: 4.4 s

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

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 69). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 953 KiB and 892 ms of main-thread time.

  • Google Tag Manager adds 431 ms

    431 ms

    Google Tag Manager costs a phone 431 ms of main-thread work and 511 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.

  • Render-blocking requests

    450 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

  • Improve image delivery

    204 KiB

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

  • 13 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 27 KiB

    About 27 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 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: 3 ms

    3 ms

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

Core Web Vitals

7 to fix57
  • Largest Contentful Paint: 10.8 s

    10.8 s

    Your largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “serious brands”.

  • Time to Interactive: 12.4 s

    12.4 s

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

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

    +48%

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

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

    +27%

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

  • Total Blocking Time: 369 ms

    369 ms

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

  • 15 images without width and height

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

  • Speed Index: 3.6 s

    3.6 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0.018

    0.018

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

Images and page weight

1 to fix70
  • Page weight: 6.1 MB in 81 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 81 requests on a phone: media 4.4 MB (3), scripts 981 KiB (22) and images 604 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • About 1.7 g of CO₂ per visit

    1.74 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

3 to fixGoogle 10097
  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 12 links without text

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

  • ARIA role should be appropriate for the element (12 elements)

    ARIA role should be appropriate for the element: 12 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 88 images in the HTML carry an alt attribute.

  • 56 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 133 internal links, 17 external

    The homepage links to 133 pages on arcticleaf.com and 17 external pages.

7 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Arctic Leaf is a Shopify Premier Partner agency. We design, build and grow Shopify Plus stores, with Baymard-certified …”.

  • One H1 headline

    Your main headline reads: “built forserious brands”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Shopify Plus Agency for Growing Brands | Arctic Leaf”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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://www.arcticleaf.com/sitemap-index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.arcticleaf.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Organization data: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix98
  • 4 pages share a meta description

    https://www.arcticleaf.com/acquisition, https://www.arcticleaf.com/conversion, https://www.arcticleaf.com/loyalty and https://www.arcticleaf.com/integrations use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 39 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

1 to fixGoogle 9693
  • 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • A 9-field form

    Your longest form asks for 9 fields (8 required). Every extra field lowers completion.

  • 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 1,190 words of copy

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START A PROJECT”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”, “Start a project” and “Subscribe”.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Hotjar, HubSpot and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • 27 other companies contacted

    Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 arcticleaf.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Astro
Analytics
Google Analytics | Google Tag Manager | Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on arcticleaf.com, including 14 speed issues, 1 SEO issue and 1 conversion gap. 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