Website review, no card needed

giantlifting.com logo

giantlifting.com website review

Visit site (opens in a new tab)Reviewed 9 November 202628 issues · 76 checks

This review found 28 issues worth fixing on giantlifting.com, 8 of them high impact, across 76 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.1 s812 msMay 23Nov 7849 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.1 s
May 30, 2026973 ms
Jun 6, 2026931 ms
Jun 13, 2026876 ms
Jun 20, 2026920 ms
Jun 27, 20261.0 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.0 s
Aug 1, 2026994 ms
Aug 8, 2026951 ms
Aug 15, 2026920 ms
Aug 22, 2026890 ms
Aug 29, 2026899 ms
Sep 5, 2026911 ms
Sep 12, 2026946 ms
Sep 19, 2026946 ms
Sep 26, 2026911 ms
Oct 3, 2026895 ms
Oct 10, 2026878 ms
Oct 17, 2026885 ms
Oct 24, 2026882 ms
Oct 31, 2026857 ms
Nov 7, 2026849 ms
Real-visitor tap response (INP)75th percentile, phones
116 ms82 msMay 23Nov 7111 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202686 ms
May 30, 202687 ms
Jun 6, 202691 ms
Jun 13, 202695 ms
Jun 20, 202695 ms
Jun 27, 202696 ms
Jul 4, 202697 ms
Jul 11, 202699 ms
Jul 18, 2026100 ms
Jul 25, 2026100 ms
Aug 1, 2026101 ms
Aug 8, 2026103 ms
Aug 15, 2026104 ms
Aug 22, 2026104 ms
Aug 29, 2026106 ms
Sep 5, 2026106 ms
Sep 12, 2026104 ms
Sep 19, 2026108 ms
Sep 26, 2026107 ms
Oct 3, 2026111 ms
Oct 10, 2026112 ms
Oct 17, 2026112 ms
Oct 24, 2026111 ms
Oct 31, 2026109 ms
Nov 7, 2026111 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 giantlifting.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix59
  • Reduce unused JavaScript

    3.4 s · 628 KiB

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

  • Use efficient cache lifetimes

    3.3 s · 557 KiB

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

  • Render-blocking requests

    1.1 s

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Improve image delivery

    800 ms · 439 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (route.com, rebuyengine.com and Shopify and others), adding 5.1 MB and 587 ms of main-thread time.

  • Mobile performance score: 59

    59/100

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

  • Shopify adds 95 ms

    95 ms

    Shopify costs a phone 95 ms of main-thread work and 4.2 MB 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.

  • 3 long tasks on the main thread

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

  • route.com adds 290 ms

    290 ms

    route.com costs a phone 290 ms of main-thread work and 542 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.

  • rebuyengine.com adds 151 ms

    151 ms

    rebuyengine.com costs a phone 151 ms of main-thread work and 298 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

    230 ms · 59 KiB

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

  • Legacy JavaScript

    200 ms · 44 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 13 ms

    13 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 14.1 s

    14.1 s

    Your largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “man with dumbbells in each hand with a white. power rack be…”.

  • Time to Interactive: 14.2 s

    14.2 s

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

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

    +27%

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 5.6 s

    5.6 s

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

  • Total Blocking Time: 293 ms

    293 ms

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

8 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.1 s

    1.1 s

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

  • Real-user INP: 98 ms

    98 ms

    Real visitors wait 98 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.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: 538 ms

    538 ms

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

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

    -18%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.8 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).

Images and page weight

1 to fix70
  • Page weight: 9.0 MB in 200 requests

    9.0 MB

    Your homepage downloads 9.0 MB in 200 requests on a phone: media 6.1 MB (1), scripts 1.2 MB (64) and other files 738 KiB (90). Under 2 MB keeps phones on slow connections fast.

  • About 2.5 g of CO₂ per visit

    2.54 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.54 g of CO₂e: 304.9 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

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

2 checks passed
  • Every image has alt text

    All 30 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 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

4 to fixGoogle 10082
  • Title is long (79 characters)

    Your title is 79 characters, so Google will cut it off around 60: “GIANT LIFTING // STRENGTH & CONDITIONING EQUIPMENT MANUFACTURER – Giant Lifting”.

  • Meta description is long (166 characters)

    Your meta description is 166 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 favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 172 internal links, 0 external

    The homepage links to 172 pages on giantlifting.com and 0 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Giant Lifting”.

  • Canonical URL set

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

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

  • llms.txt published

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

Other pages

1 to fix95
  • 4 pages without a meta description

    https://giantlifting.com/collections/all, https://giantlifting.com/collections/barbell-accessories, https://giantlifting.com/collections/lat-row-machine and https://giantlifting.com/collections/sandbags have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 78 found) and read each the way a search engine does.

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

  • 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
  • 2 JavaScript errors while loading

    2 errors were 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

  • No analytics detected

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

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

    The homepage carries about 375 words of visible text.

3 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop All Products”, “SHOP AXIS HALF RACK” and “SHOP SPECIALTY BARS”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and a star rating.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 1 more (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.

  • 16 cookies set on arrival

    16

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

  • 26 other companies contacted

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

Apps your storefront loads

Judge Me Reviews · Klaviyo Email Marketing Sms · Ta Labels Badges · Buddha Mega Menu Navigation · Restockrocket · postaffiliatepro.com · govx.com · lobuybtn.com · route.com · rebuyengine.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

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 28 issues on giantlifting.com, including 16 speed issues, 4 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
giantlifting.com website review: scores and fixes