Website review, no card needed

shiftpod.com logo

shiftpod.com website review

Visit site (opens in a new tab)Reviewed 17 November 202631 issues · 77 checks

This review found 31 issues worth fixing on shiftpod.com, 8 of them high impact, across 77 checks. The most urgent: improve image delivery. 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.2 s816 msMay 30Nov 141.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.1 s
Jun 6, 20261.0 s
Jun 13, 2026962 ms
Jun 20, 2026938 ms
Jun 27, 2026924 ms
Jul 4, 2026959 ms
Jul 11, 2026961 ms
Jul 18, 2026960 ms
Jul 25, 2026974 ms
Aug 1, 2026953 ms
Aug 8, 2026950 ms
Aug 15, 2026953 ms
Aug 22, 2026944 ms
Aug 29, 2026967 ms
Sep 5, 2026960 ms
Sep 12, 2026940 ms
Sep 19, 2026925 ms
Sep 26, 2026883 ms
Oct 3, 2026860 ms
Oct 10, 2026860 ms
Oct 17, 2026860 ms
Oct 24, 2026916 ms
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Nov 14, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
107 ms83 msMay 30Nov 1495 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202696 ms
Jun 6, 202696 ms
Jun 13, 202696 ms
Jun 20, 202696 ms
Jun 27, 202696 ms
Jul 4, 202696 ms
Jul 11, 202699 ms
Jul 18, 2026100 ms
Jul 25, 2026103 ms
Aug 1, 2026104 ms
Aug 8, 202697 ms
Aug 15, 202696 ms
Aug 22, 202688 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202686 ms
Oct 17, 202687 ms
Oct 24, 202688 ms
Oct 31, 202695 ms
Nov 7, 202696 ms
Nov 14, 202695 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 shiftpod.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix65
  • Improve image delivery

    2.9 s · 1.4 MB

    12 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, monkcommerce.app and Attentive and others), adding 14.0 MB and 820 ms of main-thread time.

  • Shopify adds 61 ms

    61 ms

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

  • Reduce unused JavaScript

    450 ms · 716 KiB

    About 716 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Use efficient cache lifetimes

    1.0 MB

    18 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

  • Mobile performance score: 65

    65/100

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

  • Render-blocking requests

    750 ms

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

  • Main-thread work: 3.3 s

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

  • Google Tag Manager adds 234 ms

    234 ms

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

  • Attentive adds 124 ms

    124 ms

    Attentive costs a phone 124 ms of main-thread work and 1.1 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.

  • monkcommerce.app adds 175 ms

    175 ms

    monkcommerce.app costs a phone 175 ms of main-thread work and 553 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 144 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    41 KiB

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

  • Minify JavaScript

    12 KiB

    12 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

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

    6 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 8.8 s

    8.8 s

    Your largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 20.2 s

    20.2 s

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

  • Speed Index: 5.0 s

    5.0 s

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

  • Total Blocking Time: 299 ms

    299 ms

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

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

    1.4 s

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

  • Real-user INP: 87 ms

    87 ms

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

    0.8 s

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

  • Real-user TTFB: 518 ms

    518 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

2 to fix64
  • Page weight: 17.0 MB in 409 requests

    17.0 MB

    Your homepage downloads 17.0 MB in 409 requests on a phone: media 11.7 MB (1), images 1.9 MB (17) and scripts 1.7 MB (105). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • About 4.8 g of CO₂ per visit

    4.81 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 8995
  • 3 text elements with low contrast

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

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 17 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 18 WCAG 2.2 A/AA and best-practice rules on the phone render: 17 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 9288
  • Meta description is long (219 characters)

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

  • 4 links with vague text

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

  • One H1 headline

    Your <h1> is empty.

  • 52 internal links, 10 external

    The homepage links to 52 pages on shiftpod.com and 10 external pages.

6 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “SHIFTPOD - Built for Wherever Your Adventures Take You”.

  • Canonical URL set

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

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

  • llms.txt published

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

Other pages

6 to fix50
  • 1 page without a title

    https://shiftpod.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    https://shiftpod.com/products/shiftpodiii declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 1 linked page hidden from search

    https://shiftpod.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://shiftpod.com/products/shiftpodiii all use the title “SHIFTPOD - Built for Wherever Your Adventures Take You”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://shiftpod.com/collections/all, https://shiftpod.com/customer_authentication/redirect, https://shiftpod.com/collections/all-products, https://shiftpod.com/policies/shipping-policy, https://shiftpod.com/collections/shelters and https://shiftpod.com/collections/gear and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://shiftpod.com/customer_authentication/redirect has 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 28 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

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

  • Only about 197 words

    The homepage has only about 197 words of visible text; thin pages give Google and first-time buyers little to go on.

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “SHOP NOW”, “Learn More” and “LEARN MORE”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 1 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.

  • 44 other companies contacted

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

Apps your storefront loads

Sc Easy 404 Ai Redirects · Gempages Builder · Attentive · Hulk Contact Form Builder · Klaviyo Email Marketing Sms · Monk Free Gift With Purchase · Deliverr Fast Tags · govx.com · orderlogicapp.com · nofraud.com · Selleasy · attn.tv · cloudfront.net

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

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 shiftpod.com, including 15 speed issues, 3 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