Website review, no card needed
shamrockrovers.ie website review
Visit site (opens in a new tab)Reviewed 18 October 202618 issues · 76 checks
This review found 18 issues worth fixing on shamrockrovers.ie, 3 of them high impact, across 76 checks. The most urgent: 2 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
92A- #981 of 126,458 reviewed websitesbeats 99%
- #354 of 70,479 online storesbeats 99%
- #335 of 63,977 Shopify storesbeats 99%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.9 s |
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 968 ms |
| Sep 19, 2026 | 960 ms |
| Sep 26, 2026 | 972 ms |
| Oct 3, 2026 | 948 ms |
| Oct 10, 2026 | 986 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 136 ms |
| May 2, 2026 | 134 ms |
| May 9, 2026 | 135 ms |
| May 16, 2026 | 132 ms |
| May 23, 2026 | 135 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 135 ms |
| Jun 20, 2026 | 133 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 132 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 141 ms |
| Aug 8, 2026 | 143 ms |
| Aug 15, 2026 | 136 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 109 ms |
| Sep 12, 2026 | 108 ms |
| Sep 19, 2026 | 110 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 111 ms |
| Oct 10, 2026 | 119 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
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.2 s
2.7 s
3.2 s
3.8 s
4.3 s
Speed
Improve image delivery
350 ms · 1.2 MB8 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Render-blocking requests
350 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
2 third-party services on the page
2 third-party services load with your homepage (Cloudflare and Shopify), adding 1.2 MB and 8 ms of main-thread time.
Shopify adds 0 ms
0 msShopify costs a phone 0 ms of main-thread work and 1.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.
Use efficient cache lifetimes
12 KiB4 files are served with short cache lifetimes, so returning visitors download them again (12 KiB).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
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.
3 checks passed
Mobile performance score: 90
90/100Your mobile performance score is 90 (desktop: 95). That is in Google's “good” band (90 and up).
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 55 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 3.3 s
3.3 sYour largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Inside Tallaght Stadium before a Shamrock Rovers UEFA Champ…”. Most of its time is element render delay (2.0 s).
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
12 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 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 95 ms
95 msReal visitors wait 95 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 379 ms
379 msReal visitors wait 379 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 136 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 51% faster for real visitors
-51%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Time to Interactive: 3.4 s
3.4 sThe page is fully interactive after 3.4 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
A-1_1_a7b32ec2-7ea9-4766-99dd-0924b640ce84.jpg weighs 787 KiB. On a phone connection a single image that size takes seconds.
6 images far larger than shown
1.1 MB6 images are downloaded at several times the size a phone draws them, for example A-1_1_a7b32ec2-7ea9-4766-99dd-0924b640ce84.jpg at 4,007 px wide, shown at 148 px. Resized copies would save about 1.1 MB.
2 images in older formats
2 images (228 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.4 g of CO₂ per visit
0.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.42 g of CO₂e: 50.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.5 MB in 32 requests
1.5 MBYour homepage downloads 1.5 MB in 32 requests on a phone: images 1.4 MB (12), HTML 29 KiB (1) and fonts 25 KiB (2). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
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 (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (18 characters)
Your title is only 18 characters: “Shamrock Rovers FC”. Between 30 and 65 characters leaves room to say what you do and for whom.
82 internal links, 47 external
The homepage links to 82 pages on shamrockrovers.ie and 47 external pages.
7 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “The official home of Shamrock Rovers FC - Ireland’s most successful football club. News, fixtures, tickets, the Rovers …”.
One H1 headline
Your main headline reads: “Shamrock Roversv Sligo Rovers”.
Canonical URL set
The canonical URL is https://www.shamrockrovers.ie/.
Structured data in place
Structured data found: SportsTeam 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://www.shamrockrovers.ie/sitemap-index.xml.
AI search readiness
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://www.shamrockrovers.ie/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 (940 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
51 of 55 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 24 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 871 words of copy
The homepage carries about 871 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact” and “Shop”.
16 calls to action
The homepage has 16 calls to action, for example “Contact”, “Shop” and “Buy Tickets”.
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Meta Pixel and Cloudflare Web Analytics.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
2 other companies contacted
Loading the homepage contacts 2 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 shamrockrovers.ie, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- Astro
- E-commerce
- Shopify
Company
- Founded
- 1901
- Headquarters
- Dublin
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on shamrockrovers.ie, including 7 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.