Website review, no card needed

prorollers.net logo

prorollers.net website review

Visit site (opens in a new tab)Reviewed 16 November 202621 issues · 73 checks

This review found 21 issues worth fixing on prorollers.net, 3 of them high impact, across 73 checks. The most urgent: 31 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 s502 msMay 30Nov 14990 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026723 ms
Jun 6, 2026725 ms
Jun 13, 2026710 ms
Jun 20, 2026709 ms
Jun 27, 2026723 ms
Jul 4, 2026732 ms
Jul 11, 2026732 ms
Jul 18, 2026738 ms
Jul 25, 2026733 ms
Aug 1, 2026742 ms
Aug 8, 2026758 ms
Aug 15, 2026776 ms
Aug 22, 2026798 ms
Aug 29, 2026796 ms
Sep 5, 2026797 ms
Sep 12, 2026776 ms
Sep 19, 2026706 ms
Sep 26, 2026646 ms
Oct 3, 2026596 ms
Oct 10, 2026566 ms
Oct 17, 2026567 ms
Oct 24, 2026569 ms
Oct 31, 2026664 ms
Nov 7, 2026806 ms
Nov 14, 2026990 ms
Real-visitor tap response (INP)75th percentile, phones
141 ms70 msMay 30Nov 14124 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202678 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202680 ms
Jul 25, 202686 ms
Aug 1, 202687 ms
Aug 8, 202696 ms
Aug 15, 2026104 ms
Aug 22, 2026111 ms
Aug 29, 2026112 ms
Sep 5, 2026109 ms
Sep 12, 2026106 ms
Sep 19, 2026101 ms
Sep 26, 2026104 ms
Oct 3, 2026112 ms
Oct 10, 2026117 ms
Oct 17, 2026127 ms
Oct 24, 2026133 ms
Oct 31, 2026129 ms
Nov 7, 2026128 ms
Nov 14, 2026124 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 prorollers.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix52
  • Mobile performance score: 52

    52/100

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

  • Render-blocking requests

    900 ms

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

  • Improve image delivery

    400 ms · 120 KiB

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

  • 1,703 HTML elements

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

  • Shopify adds 4 ms

    4 ms

    Shopify costs a phone 4 ms of main-thread work and 520 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

    150 ms · 29 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, shop.app and Key CDN and others), adding 534 KiB and 4 ms of main-thread time.

  • Use efficient cache lifetimes

    6 KiB

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

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 12 ms

    12 ms

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

Core Web Vitals

5 to fix100
  • Cumulative Layout Shift: 0.884

    0.884

    The layout shifts by 0.884 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest Contentful Paint: 6.9 s

    6.9 s

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

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

    +61%

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

  • Largest content (LCP) got 24% slower for real visitors

    +24%

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

  • Time to Interactive: 7.0 s

    7.0 s

    The page becomes fully interactive after 7.0 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.0 s

    1.0 s

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

  • Real-user INP: 124 ms

    124 ms

    Real visitors wait 124 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: 425 ms

    425 ms

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Speed Index: 2.0 s

    2.0 s

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

  • 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 fix90
  • 5 images far larger than shown

    400 KiB

    5 images are downloaded at several times the size a phone draws them, for example Bat_rolling.webp at 1,080 px wide, shown at 80 px. Resized copies would save about 400 KiB.

  • 5 images in older formats

    5 images (421 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.3 g of CO₂ per visit

    0.31 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.31 g of CO₂e: 37.4 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.1 MB in 68 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 68 requests on a phone: scripts 475 KiB (27), images 370 KiB (13) and HTML 134 KiB (1). That is a lean page.

  • Images load when needed

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

Accessibility

5 to fixGoogle 9594
  • 31 text elements with low contrast

    31 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 (5 elements)

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor 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.

  • Headings skip levels

    Headings skip levels (h1 → h5, h2 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 46 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: 46 passed and 5 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 10089
  • Title is long (102 characters)

    Your title is 102 characters, so Google will cut it off around 60: “ProRollers: Heat-Rolled Bats & Game-Ready Baseball Gloves – ProRollers Rolled Bats & Game…”.

  • Structured data has 8 problems

    Structured data found (SportingGoodsStore, VideoObject and WebSite) but with 8 problems, for example “VideoObject: contentUrl is not an absolute URL ("//prorollers.net/cdn/shop/videos/c/vp/be7d7a9d3225…”.

  • 198 internal links, 6 external

    The homepage links to 198 pages on prorollers.net and 6 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Shop ProRollers for professionally heat-rolled baseball and softball bats, game-ready gloves, and Patriot bat rollers. …”.

  • One H1 headline

    Your main headline reads: “Heat Rolled Bats & Game Ready Gloves”.

  • Canonical URL set

    The canonical URL is https://prorollers.net/.

  • 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://prorollers.net/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://prorollers.net/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,284 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    3 pages of 15 loaded without an error (the rest turned automated requests away).

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    30 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

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

    The homepage carries about 924 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact” and “Shop Now”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Contact”, “Shop Now” and “Shop Our Newest Game Ready Gear”.

  • 8 short forms

    8 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 26 testimonial or review blocks and 1 trust badge.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 5 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 prorollers.net, 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

Visually A B Testing Cro · Inbox · Route Protection Tracking · Searchanise Search Filter · Ez Terms And Conditions Checkbox · Google Reviews · Bayengage · Smart Menu · Easify Product Options · Bayrewards · targetbay.com · nfcube.com · elfsight.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 21 issues on prorollers.net, including 10 speed issues, 2 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