Website review, no card needed

shop-task.com logo

shop-task.com website review

Visit site (opens in a new tab)Reviewed 8 November 202625 issues · 79 checks

This review found 25 issues worth fixing on shop-task.com, 4 of them high impact, across 79 checks. The most urgent: 2 text elements 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.1 s858 msMay 16Oct 31890 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.0 s
May 30, 2026934 ms
Jun 6, 2026893 ms
Jun 13, 2026920 ms
Jun 20, 2026954 ms
Jun 27, 2026976 ms
Jul 4, 2026984 ms
Jul 11, 2026959 ms
Jul 18, 2026967 ms
Jul 25, 2026952 ms
Aug 1, 2026978 ms
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 2026993 ms
Sep 5, 2026927 ms
Sep 12, 2026937 ms
Sep 19, 2026917 ms
Sep 26, 2026899 ms
Oct 3, 2026939 ms
Oct 10, 2026939 ms
Oct 17, 2026931 ms
Oct 24, 2026912 ms
Oct 31, 2026890 ms
Real-visitor tap response (INP)75th percentile, phones
102 ms78 msMay 16Oct 3197 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202688 ms
May 23, 202686 ms
May 30, 202682 ms
Jun 6, 202681 ms
Jun 13, 202685 ms
Jun 20, 202685 ms
Jun 27, 202686 ms
Jul 4, 202686 ms
Jul 11, 202687 ms
Jul 18, 202690 ms
Jul 25, 202694 ms
Aug 1, 202698 ms
Aug 8, 202697 ms
Aug 15, 202697 ms
Aug 22, 202694 ms
Aug 29, 202689 ms
Sep 5, 202689 ms
Sep 12, 202690 ms
Sep 19, 202692 ms
Sep 26, 202695 ms
Oct 3, 202696 ms
Oct 10, 202699 ms
Oct 17, 202698 ms
Oct 24, 202695 ms
Oct 31, 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 shop-task.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix75
  • Mobile performance score: 75

    75/100

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

  • Improve image delivery

    150 ms · 262 KiB

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

  • 1,604 HTML elements

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

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

  • Render-blocking requests

    150 ms

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, geotargetly.co and Google Fonts and others), adding 283 KiB and 51 ms of main-thread time.

  • Use efficient cache lifetimes

    54 KiB

    8 files are served with short cache lifetimes, so returning visitors download them again (54 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

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

4 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: 5.7 s

    5.7 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

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

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

    +10%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 88 ms to 97 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: 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: 95 ms

    95 ms

    Real visitors wait 95 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: 0.7 s

    0.7 s

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

  • Real-user TTFB: 461 ms

    461 ms

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

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

    -15%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    WIZARD-GENERAL-PURPOSE-SKATES-DELFINO1.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).

  • 2 images in older formats

    2 images (110 KiB) are 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.5 g of CO₂ per visit

    0.53 g

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

2 checks passed
  • Page weight: 1.9 MB in 201 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 201 requests on a phone: other files 934 KiB (136), images 642 KiB (23) and scripts 237 KiB (35). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9695
  • 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.

  • All page content should be contained by landmarks (12 elements)

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 20 links without text

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

  • 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 31 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

2 to fixGoogle 10085
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (272 characters)

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

  • 107 internal links, 7 external

    The homepage links to 107 pages on shop-task.com and 7 external pages.

6 checks passed
  • Title: 50 characters

    Your title is a healthy 50 characters: “SHOP TASK | Canada's inline skate shop since 2005.”.

  • Canonical URL set

    The canonical URL is https://shop-task.com/en-us.

  • 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://shop-task.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 (359 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix76
  • 2 pages share a title

    https://shop-task.com/en-us/collections/general-purpose-inline-skates and https://shop-task.com/collections/general-purpose-inline-skates-men all use the title “Inline Skates for General Purpose – SHOP TASK”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://shop-task.com/en-us/pages/about-us, https://shop-task.com/en-us/pages/inline-skate-parts, https://shop-task.com/en-us/collections/sale-1, https://shop-task.com/en-us/collections/wheels, https://shop-task.com/en-us/collections/bearings-1 and https://shop-task.com/en-us/collections/frames-1 and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://shop-task.com/en-us/collections/general-purpose-inline-skates and https://shop-task.com/collections/general-purpose-inline-skates-men use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://shop-task.com/collections/general-purpose-inline-skates-men, whose canonical is https://shop-task.com/en-us/collections/general-purpose-inline-skates. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://shop-task.com/en-us/pages/locations, https://shop-task.com/en-us/pages/about-us and https://shop-task.com/en-us/pages/accessories-collection-listing 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 65 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 10093
  • 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_TUNNEL_CONNECTION_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • 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: 1 testimonial or review block. 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.

  • No opening hours

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

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

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

  • About 430 words of copy

    The homepage carries about 430 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Got questions? Contact us.” and “[email protected]”.

  • 3 short forms

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

  • Phone number on the homepage

    Your phone number is on the homepage.

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.

  • 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 shop-task.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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Reputon Google Reviews Widget · geotargetly.co

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on shop-task.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