Website review, no card needed
blinds-2go.ie website review
Visit site (opens in a new tab)Reviewed 5 November 202633 issues · 93 checks
This review found 33 issues worth fixing on blinds-2go.ie, 12 of them high impact, across 93 checks. The most urgent: page weight: 20.3 MB in 352 requests. 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
84B- #22,533 of 126,442 reviewed websitesbeats 77%
- #14,355 of 70,471 online storesbeats 74%
- #13,912 of 63,968 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 229 ms |
| May 23, 2026 | 230 ms |
| May 30, 2026 | 234 ms |
| Jun 6, 2026 | 230 ms |
| Jun 13, 2026 | 226 ms |
| Jun 20, 2026 | 214 ms |
| Jun 27, 2026 | 204 ms |
| Jul 4, 2026 | 198 ms |
| Jul 11, 2026 | 196 ms |
| Jul 18, 2026 | 202 ms |
| Jul 25, 2026 | 208 ms |
| Aug 1, 2026 | 213 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 221 ms |
| Aug 22, 2026 | 221 ms |
| Aug 29, 2026 | 223 ms |
| Sep 5, 2026 | 223 ms |
| Sep 12, 2026 | 225 ms |
| Sep 19, 2026 | 222 ms |
| Sep 26, 2026 | 219 ms |
| Oct 3, 2026 | 213 ms |
| Oct 10, 2026 | 210 ms |
| Oct 17, 2026 | 210 ms |
| Oct 24, 2026 | 209 ms |
| Oct 31, 2026 | 213 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
1.1 s
2.2 s
3.3 s
4.4 s
5.6 s
6.7 s
7.8 s
8.9 s
Speed
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.8 s
A phone's processor spends 7.8 s on main-thread work while loading, 4.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, decagon.ai and opticksprotection.com and others), adding 1.8 MB and 2.0 s of main-thread time.
Improve image delivery
300 ms · 1.3 MB27 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
900 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused JavaScript
628 KiBAbout 628 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 560 ms
560 msGoogle Tag Manager costs a phone 560 ms of main-thread work and 531 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.
decagon.ai adds 499 ms
499 msdecagon.ai costs a phone 499 ms of main-thread work and 699 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
300 ms · 115 KiBAbout 115 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 358 ms. During a long task the page ignores taps.
opticksprotection.com adds 303 ms
303 msopticksprotection.com costs a phone 303 ms of main-thread work and 34 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.
ContentSquare adds 275 ms
275 msContentSquare costs a phone 275 ms of main-thread work and 158 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.
2,575 HTML elements
The page has 2,575 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
211 KiB16 files are served with short cache lifetimes, so returning visitors download them again (211 KiB).
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 32.8 s
32.8 sThe page becomes fully interactive after 32.8 s. Good is under 3.8 s.
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 229 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 156 ms
156 msReal visitors wait 156 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 423 ms
423 msReal visitors wait 423 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.03
0.03The layout barely moves while loading (CLS 0.03, good is under 0.1).
Images and page weight
Page weight: 20.3 MB in 352 requests
20.3 MBYour homepage downloads 20.3 MB in 352 requests on a phone: media 13.5 MB (2), images 2.7 MB (55) and scripts 2.0 MB (158). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
BlackoutGIF-1.gif weighs 524 KiB. On a phone connection a single image that size takes seconds.
3 images in older formats
3 images (1.1 MB) 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 5.8 g of CO₂ per visit
5.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.77 g of CO₂e: 691.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
ARIA attributes must conform to valid values (4 elements)
ARIA attributes must conform to valid values: 4 elements on the page fail this check, rated critical by axe-core.
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
73 images without alt text
73 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail 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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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.
Headings skip levels
Headings skip levels (h2 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
521 internal links, 15 external
The homepage links to 521 pages on blinds-2go.ie and 15 external pages.
8 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Order quality made to measure blinds online at Blinds2Go. Wooden, Roman, Roller Blinds plus more with free samples and …”.
One H1 headline
Your main headline reads: “Made to measure blinds & curtains”.
Title: 61 characters
Your title is a healthy 61 characters: “Blinds2Go Ireland | Made to Measure Blinds & Incredible Value”.
Canonical URL set
The canonical URL is https://www.blinds-2go.ie/.
Structured data in place
Structured data found: OnlineStore, Organization, WebPage 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.blinds-2go.ie/sitemap.xml.
AI search readiness
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,143 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.blinds-2go.ie/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 156 found) and read each the way a search engine does.
7 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 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 14 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
53 of 55 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 827 words of copy
The homepage carries about 827 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us” and “Sign up”.
26 calls to action
The homepage has 26 calls to action, for example “Contact Us”, “Shop All Roller Blinds” and “Shop All Roman Blinds”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks, a star rating and “Over 200,000 happy customers”.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
20 cookies set on arrival
20Opening the homepage sets 20 cookies (measured from a US location before any click).
22 other companies contacted
Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 blinds-2go.ie, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on blinds-2go.ie, including 17 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.