Programmable

Website review, no card needed

getblaster.co logo

getblaster.co website review

Visit site (opens in a new tab)Reviewed 12 November 202624 issues · 79 checks

This review found 24 issues worth fixing on getblaster.co, 4 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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

Site score

92A

Closest competitors among Shopify stores

Compare side by side

One score from every part of this review. How it works

shellblaster.co (opens in a new tab)
Full-page screenshot of getblaster.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. getblaster.co at 0.4 s0.4 s
  2. getblaster.co at 0.9 s0.9 s
  3. getblaster.co at 1.3 s1.3 s
  4. getblaster.co at 1.8 s1.8 s
  5. getblaster.co at 2.2 s2.2 s
  6. getblaster.co at 2.7 s2.7 s
  7. getblaster.co at 3.1 s3.1 s
  8. getblaster.co at 3.5 s3.5 s

Speed

4 to fix82

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 82

    82/100

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

  • Reduce unused CSS

    300 ms · 57 KiB

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

  • 1,785 HTML elements

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

  • Reduce unused JavaScript

    150 ms · 78 KiB

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

  • Improve image delivery

    189 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (shrinetheme.com, Shopify and config-security.com and others), adding 306 KiB and 54 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Duplicated JavaScript

    10 KiB

    10 KiB JavaScript is shipped twice across bundles.

  • Use efficient cache lifetimes

    9 KiB

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed

  • Main-thread work: 1.8 s

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

  • Server response: 19 ms

    19 ms

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

Core Web Vitals

2 to fix100

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.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: 4.8 s

    4.8 s

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

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: 1.7 s

    1.7 s

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

  • Real-user INP: 129 ms

    129 ms

    Real visitors wait 129 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.4 s

    1.4 s

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.057

    0.057

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

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 45 ms

    45 ms

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

Images and page weight

2 to fix80

  • 3 images in older formats

    3 images (546 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.

  • 1 image far larger than shown

    30 KiB

    1 image is downloaded at several times the size a phone draws it, for example gb-h3-hero-bf.webp at 1,376 px wide, shown at 390 px. Resized copies would save about 30 KiB.

  • About 0.6 g of CO₂ per visit

    0.56 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.56 g of CO₂e: 67.5 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: 2.0 MB in 176 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 176 requests on a phone: other files 801 KiB (86), images 479 KiB (14) and scripts 398 KiB (51). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 9794

  • 1 text element with low contrast

    1 text element doesn'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.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

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

2 checks passed

  • Every image has alt text

    All 93 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 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096

  • Structured data has 1 problem

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

  • 93 internal links, 1 external

    The homepage links to 93 pages on getblaster.co and 1 external page.

7 checks passed

  • Meta description: 148 characters

    Your meta description is 148 characters: “Shop realistic toy blasters that load, fire & eject shells. Soft plastic darts, electric water blasters & brick-built b…”.

  • One H1 headline

    Your main headline reads: “@media screen and (max-width: 749px) { .header__heading-logo--main-desktop { display: none !important; } .header__headi…”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Shellblaster — Realistic Toy Blasters & Shell Ejecting Toy Guns”.

  • Canonical URL set

    The canonical URL is https://shellblaster.co/.

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

  • llms.txt published

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

Other pages

5 to fix60

  • 1 page without a title

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

  • 2 linked pages hidden from search

    https://shellblaster.co/pages/build-your-bundle and https://shellblaster.co/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://shellblaster.co/products/raven and https://shellblaster.co/products/raven-classic-shellblaster all use the title “Raven Shellblaster”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://shellblaster.co/pages/build-your-bundle, https://shellblaster.co/collections/shell-blasters, https://shellblaster.co/pages/target-range, https://shellblaster.co/collections/water-blaster, https://shellblaster.co/pages/about-us and https://shellblaster.co/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://shellblaster.co/pages/target-range, https://shellblaster.co/apps/track123 and https://shellblaster.co/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://shellblaster.co/pages/target-range 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.

  • 3 pages slow to respond

    https://shellblaster.co/pages/build-your-bundle, https://shellblaster.co/collections/water-blaster and https://shellblaster.co/collections/accessories took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

Best practices

Google 96100
3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86

  • No analytics detected

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

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

  • About 1,037 words of copy

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE SALE” and “Shop all →”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Contact Us”, “Track Order” and “SHOP THE SALE”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 126 testimonial or review blocks, 3 customer or partner logos, a star rating and “3,100+ reviews”.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix

  • 6 trackers load before any consent

    6

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

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies, 2 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.

  • 24 other companies contacted

    Loading the homepage contacts 24 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 getblaster.co, 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

Triplewhale · Judge Me Reviews · Blaster Checkout Countdown · Simprosys Google Shopping Feed

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 24 issues on getblaster.co, including 6 speed issues, 1 SEO issue 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