Website review, no card needed
siruishop.de website review
Visit site (opens in a new tab)Reviewed 7 November 202640 issues · 93 checks
This review found 40 issues worth fixing on siruishop.de, 14 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. 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
78C- #53,058 of 104,401 reviewed websitesbeats 44%
- #34,300 of 58,402 online storesbeats 36%
- #32,761 of 53,185 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 97 ms |
| May 23, 2026 | 103 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 115 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 118 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 163 ms |
| Aug 29, 2026 | 155 ms |
| Sep 5, 2026 | 151 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 147 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 158 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 169 ms |
| Oct 24, 2026 | 188 ms |
| Oct 31, 2026 | 179 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
Speed
Reduce unused JavaScript
8.9 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.9 s faster on a phone.
Avoid multiple page redirects
8.9 sThe page goes through 2 redirects before it starts loading, costing about 8.9 s. Link and advertise the final URL directly.
Main-thread work: 10.1 s
A phone's processor spends 10.1 s on main-thread work while loading, 6.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, gsitrix.com and omnisnippet1.com and others), adding 3.4 MB and 2.3 s of main-thread time.
Use efficient cache lifetimes
600 ms · 698 KiB25 files are served with short cache lifetimes, so returning visitors download them again (698 KiB).
Google Tag Manager adds 917 ms
917 msGoogle Tag Manager costs a phone 917 ms of main-thread work and 1.5 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 543 ms. During a long task the page ignores taps.
gsitrix.com adds 497 ms
497 msgsitrix.com costs a phone 497 ms of main-thread work and 60 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,658 HTML elements
The page has 2,658 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google/Doubleclick Ads adds 190 ms
190 msGoogle/Doubleclick Ads costs a phone 190 ms of main-thread work and 496 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.
Shopify adds 123 ms
123 msShopify costs a phone 123 ms of main-thread work and 474 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.
xcottons.com adds 112 ms
112 msxcottons.com costs a phone 112 ms of main-thread work and 365 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.
Document request latency
250 msThe HTML itself could arrive about 250 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Improve image delivery
193 KiB12 images could be 193 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Legacy JavaScript
100 KiBPolyfills for old browsers add 100 KiB JavaScript that modern phones do not need.
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
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.
Duplicated JavaScript
5 KiB5 KiB JavaScript is shipped twice across bundles.
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: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.3 s
21.3 sYour largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 36.8 s
36.8 sThe page becomes fully interactive after 36.8 s. Good is under 3.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Tap response (INP) got 84% slower for real visitors
+84%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 97 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
22 images without width and height
22 images have no width and height attributes, so the layout jumps as each one loads.
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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 172 ms
172 msReal visitors wait 172 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 532 ms
532 msReal visitors wait 532 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.069
0.069The layout barely moves while loading (CLS 0.069, good is under 0.1).
Images and page weight
Page weight: 57.5 MB in 481 requests
57.5 MBYour homepage downloads 57.5 MB in 481 requests on a phone: media 50.7 MB (6), scripts 4.1 MB (180) and other files 1.1 MB (168). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
750x1000-1.webp 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).
1 image in older formats
1 image (72 KiB) is 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 16.3 g of CO₂ per visit
16.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 16.30 g of CO₂e: 1955.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
29 images without alt text
29 images have no alt text, which hurts accessibility and image search.
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.
24 links without text
24 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.
Headings should not be empty (6 elements)
Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
52 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: 52 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (239 characters)
Your meta description is 239 characters; Google truncates after about 160, so the end of your pitch is cut.
12 links crawlers can't follow
12 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
213 internal links, 14 external
The homepage links to 213 pages on siruishop.de and 14 external pages.
6 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “SIRUI® offizieller Onlineshop - Objektive, Stative, Leuchten”.
Canonical URL set
The canonical URL is https://siruishop.de/.
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://siruishop.de/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: 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 (1,230 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://siruishop.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://siruishop.de/collections/nach-serien-einkaufen has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://siruishop.de/products/sirui-swift-20mm-40mm-vollformat-autofokus-objektiv, https://siruishop.de/products/saturn-v2-serie-anamorphotes-vollformat-cine-objektiv, https://siruishop.de/collections/objektiv, https://siruishop.de/collections/nach-serien-einkaufen, https://siruishop.de/products/sirui-saturn-35-50-75mm-t2-9-1-6x-anamorphotes-carbon-vollformat-objektiv-for-diverse-kameraanschlosse and https://siruishop.de/products/night-walker-t1-2-s35-cine-lens-series and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://siruishop.de/products/sirui-swift-20mm-40mm-vollformat-autofokus-objektiv and https://siruishop.de/products/sirui-ironstar-1-5x-anamorphic-cine-lens-series have 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.
1 page slow to respond
https://siruishop.de/pages/exklusive-angebote took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 120 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “SyntaxError: Failed to execute 'querySelector' on 'Document': '[class*=' is not a valid selector.”.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
69 of 78 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: 1 trust badge. 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.
About 507 words of copy
The homepage carries about 507 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now>” and “Buy now”.
12 calls to action
The homepage has 12 calls to action, for example “Buy now”, “Learn More >” and “SHOP NOW”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.
25 cookies set on arrival
25Opening the homepage sets 25 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.
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 siruishop.de, 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 18 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Icart Cart Upsell · Smart Seo · T Lab Ai Translate · Tabs Studio · Ryviu Product Reviews · Convbox Analytics · Xcotton Guard · Frequently Bought · Awin Affiliate Marketing · Content Translation · Joy Loyalty Program · Omnisend · Grouptify Combined Listings · identixweb.com · cloudfront.net · avada.io · layouthub.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
- 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 40 issues on siruishop.de, including 20 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.