Website review, no card needed
rapoly.com website review
Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 77 checks
This review found 33 issues worth fixing on rapoly.com, 13 of them high impact, across 77 checks. The most urgent: render-blocking 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
78C- #50,363 of 99,098 reviewed websitesbeats 44%
- #31,930 of 54,243 online storesbeats 36%
- #30,441 of 49,214 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 205 ms |
| May 23, 2026 | 207 ms |
| May 30, 2026 | 216 ms |
| Jun 6, 2026 | 229 ms |
| Jun 13, 2026 | 232 ms |
| Jun 20, 2026 | 230 ms |
| Jun 27, 2026 | 222 ms |
| Jul 4, 2026 | 214 ms |
| Jul 11, 2026 | 214 ms |
| Jul 18, 2026 | 204 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 195 ms |
| Aug 15, 2026 | 199 ms |
| Aug 22, 2026 | 200 ms |
| Aug 29, 2026 | 199 ms |
| Sep 5, 2026 | 202 ms |
| Sep 12, 2026 | 202 ms |
| Sep 19, 2026 | 208 ms |
| Sep 26, 2026 | 213 ms |
| Oct 3, 2026 | 213 ms |
| Oct 10, 2026 | 214 ms |
| Oct 17, 2026 | 214 ms |
| Oct 24, 2026 | 218 ms |
| Oct 31, 2026 | 223 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
Render-blocking requests
2.2 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
640 ms · 263 KiBAbout 263 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 640 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, kiwisizing.com and Klaviyo and others), adding 621 KiB and 511 ms of main-thread time.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
200 ms · 244 KiB11 images could be 244 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Use efficient cache lifetimes
200 ms · 146 KiB10 files are served with short cache lifetimes, so returning visitors download them again (146 KiB).
Legacy JavaScript
100 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Reduce unused CSS
120 ms · 12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 120 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.
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.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.6 s
15.6 sYour largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Du bist genug Hoodie”.
Time to Interactive: 15.9 s
15.9 sThe page becomes fully interactive after 15.9 s. Good is under 3.8 s.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 205 ms to 223 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.6 s
1.6 sReal visitors wait 1.6 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 504 ms
504 msReal visitors wait 504 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 56 ms
56 msScripts block the page for only 56 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.3 MB in 269 requests
3.3 MBYour homepage downloads 3.3 MB in 269 requests on a phone: images 1.5 MB (35), other files 819 KiB (102) and scripts 751 KiB (87). Under 2 MB keeps phones on slow connections fast.
4 images below the first screen load straight away
4 images further down the page (128 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.93 g of CO₂e: 111.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
2 dropdowns have no label.
52 text elements with low contrast
52 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 form fields without a label
2 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 (11 elements)
Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (6 characters)
Your title is only 6 characters: “Rapoly”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
148 internal links, 0 external
The homepage links to 148 pages on rapoly.com and 0 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://rapoly.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://rapoly.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://rapoly.com/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.
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.
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 (661 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://rapoly.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://rapoly.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
/ and https://rapoly.com/apps/bestellverfolgung all use the title “Rapoly”. 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://rapoly.com/collections/all, https://rapoly.com/customer_authentication/redirect, https://rapoly.com/collections/neuheiten, https://rapoly.com/collections/gedenkgeschenke, https://rapoly.com/collections/fur-mama and https://rapoly.com/collections/fur-die-ehefrau have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://rapoly.com/customer_authentication/redirect and https://rapoly.com/apps/bestellverfolgung have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 56 found) and read each the way a search engine does.
2 checks passed
Linked pages load
7 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.
Best practices
2 broken images
2 images failed to load on a phone, for example https://rapoly.com/.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Triplewhale Survey Error: no order_id was found”.
2 checks passed
Tap targets are thumb-sized
29 of 32 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 5 testimonial or review blocks. 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 268 words of copy
The homepage carries about 268 words of visible text.
2 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 mores (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.
28 cookies set on arrival
28Opening the homepage sets 28 cookies, 1 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 rapoly.com, 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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Judge Me Reviews · Kaching Bundles · Triplewhale · Simprosys Google Shopping Feed · Gempages Builder · Gempages Cro · kiwisizing.com · web.app · archive-digger.com · richpanel.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
- Microsoft Clarity
- 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 rapoly.com, including 10 speed issues, 4 SEO issues and 4 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.