Website review, no card needed

gianttiger.com logo

gianttiger.com website review

Visit site (opens in a new tab)Reviewed 19 November 202640 issues · 87 checks

This review found 40 issues worth fixing on gianttiger.com, 17 of them high impact, across 87 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
1.6 s1.5 sMay 30Nov 141.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Nov 7, 20261.5 s
Nov 14, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
135 ms118 msMay 30Nov 14120 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026126 ms
Jun 6, 2026127 ms
Jun 13, 2026126 ms
Jun 20, 2026125 ms
Jun 27, 2026125 ms
Jul 4, 2026125 ms
Jul 11, 2026127 ms
Jul 18, 2026126 ms
Jul 25, 2026126 ms
Aug 1, 2026127 ms
Aug 8, 2026129 ms
Aug 15, 2026130 ms
Aug 22, 2026133 ms
Aug 29, 2026133 ms
Sep 5, 2026129 ms
Sep 12, 2026129 ms
Sep 19, 2026127 ms
Sep 26, 2026124 ms
Oct 3, 2026123 ms
Oct 10, 2026121 ms
Oct 17, 2026121 ms
Oct 24, 2026121 ms
Oct 31, 2026121 ms
Nov 7, 2026120 ms
Nov 14, 2026120 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 gianttiger.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gianttiger.com at 0.5 s0.5 s
  2. gianttiger.com at 1.0 s1.0 s
  3. gianttiger.com at 1.5 s1.5 s
  4. gianttiger.com at 2.0 s2.0 s
  5. gianttiger.com at 2.5 s2.5 s
  6. gianttiger.com at 2.9 s2.9 s
  7. gianttiger.com at 3.4 s3.4 s
  8. gianttiger.com at 3.9 s3.9 s

Speed

10 to fix33
  • Reduce unused JavaScript

    1.8 s · 534 KiB

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

  • Signyfyd adds 1.4 s

    1.4 s

    Signyfyd costs a phone 1.4 s of main-thread work and 536 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.2 s

    A phone's processor spends 6.2 s on main-thread work while loading, 3.9 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 (Signyfyd, Google Tag Manager and TrustArc and others), adding 1.8 MB and 2.5 s of main-thread time.

  • Improve image delivery

    1.2 MB

    26 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    450 ms · 458 KiB

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

  • Render-blocking requests

    600 ms

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

  • Google Tag Manager adds 356 ms

    356 ms

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 71 KiB

    Polyfills for old browsers add 71 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    50 ms · 43 KiB

    43 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    13 KiB

    13 KiB JavaScript is shipped twice across bundles.

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

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

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

    0.33

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

  • Largest Contentful Paint: 17.6 s

    17.6 s

    Your largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Popular Toys, Low Prices. Find the perfect gift for under t…”.

  • Time to Interactive: 25.7 s

    25.7 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • 12 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

5 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 104 ms

    104 ms

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 320 ms

    320 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 5.8 MB in 379 requests

    5.8 MB

    Your homepage downloads 5.8 MB in 379 requests on a phone: scripts 2.2 MB (157), images 2.1 MB (64) and other files 918 KiB (116). Under 2 MB keeps phones on slow connections fast.

  • 21 images below the first screen load straight away

    21 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 13 images in older formats

    13 images (1.0 MB) 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 1.6 g of CO₂ per visit

    1.64 g

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

1 checks passed
  • 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 9395
  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

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

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

    Elements with visible text labels do not have matching accessible names. (9 elements).

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 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

6 to fixGoogle 8580
  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “Home page” and “”). One clear main headline is easier for people and search engines.

  • Meta description is long (193 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 8 internal links, 0 external

    The homepage links to 8 pages on gianttiger.com and 0 external pages.

4 checks passed
  • Title: 36 characters

    Your title is a healthy 36 characters: “Giant Tiger: Low Price is What We Do”.

  • Canonical URL set

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

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

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    3%

    A phone browser shows 792 words, but the HTML your server sends has only 21. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • Organization data is thin (3 of 6 facts)

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

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

  • llms.txt published

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

Other pages

1 to fix95
  • 1 page without an H1

    https://www.gianttiger.com/collections/flyers-and-deals has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.gianttiger.com/collections/flyers-and-deals has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://www.gianttiger.com/collections/flyers-and-deals took over 3 s to send its HTML from our server.

  • 1 internal page checked

    We fetched 1 page linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 1 page 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 1 page that loaded have a meta description.

  • 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 1 page that loaded have a <title>.

Best practices

4 to fixGoogle 6970
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343071201&Ver=2&mid=568fce1d-1b30-4dd2-a6d2-9e6b048ee9fb&bo=1&sid=c3a6faf0e43211f1822401a52a89cd87&vid=c3a711b0e43211f1bb7d33eac920fd42&vids=1&msclkid=N&pi=918639831&l.

  • 10 small tap targets

    10 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 792 words of copy

    The homepage carries about 792 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Christmas Décor at Low Prices! Shop All” and “Shop toys & games”.

  • 1 call to action

    The homepage has 1 call to action, for example “Login / Join”.

  • 13 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Segment.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies, 1 of them by other companies (measured from a US location before any click).

  • 48 other companies contacted

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

1 checks passed
  • Consent tool: TrustArc

    A consent management tool (TrustArc) 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 gianttiger.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

Klaviyo Email Marketing Sms · signifyd.com · trafficmanager.net · rakutenadvertising.io

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
Analytics
Google Analytics | Segment
Hosting
Shopify

Company

Founded
1961
Headquarters
Ottawa

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on gianttiger.com, including 18 speed issues, 6 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