Website monitoring for online shops
In a shop, downtime costs revenue, longer load times can cost conversion and a broken checkout often goes unnoticed. XICTRAQ monitors availability, the order path, speed and security — and measures your revenue cookieless.
Downtime is direct lost revenue — do the math
For an online shop an outage carries an immediately tangible price. While the site is unreachable no orders come in, ad budget from running campaigns burns on an error page and disappointed visitors often do not return. Unlike a purely informational site the lost time cannot be made up: the cart from 2:32 pm is usually gone by 3:00 pm, and the customer has long since bought elsewhere.
The simplest approximation of the cost: monthly revenue divided by selling hours. A shop with 60,000 euros a month and sales spread over roughly twelve hours a day averages about 165 euros per hour — a multiple during evening prime time. A single unnoticed hour on the wrong day quickly costs more than an entire monthly monitoring subscription. That is exactly why it matters not only that an outage happens, but how quickly you hear about it.
That is why XICTRAQ checks availability not from a single point but across three distributed EU nodes in Nuremberg, Helsinki and Falkenstein. Helsinki is in Finland and therefore in the EU. Only once several nodes confirm the same outage — the multi-node consensus — is an alert raised. This reduces false alarms from an isolated network glitch and ensures you react when it matters — via email, Slack, Telegram, Discord, Microsoft Teams or webhook. When the shop drops, the auto-diagnosis automatically gathers context: HTTP status with response time and server IP, DNS resolution, a traceroute and a screenshot, so you are not left in the dark.
Check checkout and login with assertions — not just "status 200"
Plain reachability is only half the story. A shop can respond with status 200 and still be unusable because the payment service hangs, a shipping plugin throws an error or a new script blocks the add-to-cart button. Browser monitoring runs stored scripts in real browsers and reproduces the actual order path: open a product, add to cart, go to checkout and optionally log in.
Open product
Product page loads, price and "add to cart" are visible
Add to cart
Assertion: cart counter shows 1
Optional login
Assertion: customer account name is visible
Place order
Assertion: confirmation text appears — otherwise alert, screenshot in the run
The decisive part is the assertions — check conditions that must hold after each step. After "add to cart" it checks the cart counter shows 1; after "login" the customer account name must be visible; after "place order" the confirmation text must appear. Only these conditions turn a click path into a real functional test. If an assertion fails or a step takes unusually long, you receive an alert, and a screenshot records the error state — and discover a broken checkout before the abandonment rate shows up in the numbers.
A common objection is: "My hosting already reports outages." That is true for the server, but not for the order path. A frequent scenario: an automatic plugin update swaps out the payment integration overnight, the server keeps running flawlessly, yet the payment step throws an error. Without a functional test this only surfaces when the missing orders are noticed in the morning. With a checkout browser check including an assertion on the confirmation text, XICTRAQ reports during the night — and the damage stays small.
Speed and trust decide conversion and ranking
Speed matters too. Load time and visual stability affect how many visitors stay through to purchase and are among the signals Google uses for ranking. XICTRAQ captures Core Web Vitals — LCP for rendering the largest content, CLS for unwanted layout shifts and INP for input responsiveness — from real shopper visits rather than only in a lab environment. This field data shows the actual experience on your customers devices and connections, not the flattered values of a fast test machine.
Largest Contentful Paint
Rendering of the largest content
Cumulative Layout Shift
Unwanted layout shifts
Interaction to Next Paint
Input responsiveness
Against a freely defined performance budget you can have alerts fire automatically. It applies to the address stored as the website, is set via the API and is compared with the latest Lighthouse run every six hours (desktop, mobile or both). Set, for example, an LCP budget of 2.5 seconds: if a theme update, a new tracking script or a heavy image slider pushes the value past it, the system reports — and you spot the cause before conversion visibly drops. Performance turns from a vague gut feeling into a monitored metric with a clear threshold.
Trust completes the picture. An expired SSL certificate, missing security headers or a connection flagged as insecure scare buyers off at the very moment of payment — and an expired certificate often blocks the shop entirely. The security scan checks SSL expiry, headers and known weaknesses regularly and warns in good time before a certificate expires. That way you avoid the most expensive form of a certificate problem: the silent total outage over the weekend.
Measure revenue — without cookie-banner data loss
Cookie-based tracking has a practical problem in shops: if a substantial share of visitors declines the consent banner, exactly those purchases are missing from the analysis. The numbers in the tool and the orders in the backend drift apart, and well-founded decisions about assortment, prices or campaigns get made on a data basis full of holes. XICTRAQ instead measures cookieless: orders, revenue, cart value and conversion rate are captured without setting tracking cookies; visits are told apart by a pseudonymous daily identifier. Customer recognition from the Business plan assigns logged-in customers via their customer number.
For plain reach and revenue measurement a consent banner is therefore usually not required — the legal assessment in each case remains with you. More than 25 common shop systems such as WooCommerce, Shopify, Shopware, Magento, PrestaShop or JTL are detected automatically, so e-commerce metrics mostly appear without manual setup. Logged-in customers can be matched automatically in the common systems. A lean JavaScript interface additionally lets you pass custom events deliberately — product view, cart change, individual checkout steps or the final order with amount, tax and shipping.
Because analytics, uptime, Web Vitals and browser checks come together in one interface, you can connect cause and effect: if conversion drops one afternoon, the same tool shows whether response time rose at the same time, a Web Vitals budget broke or the checkout check turned red. That is the difference between a number that gets worse and an explanation of why.
Cookieless shop analytics versus consent-bound tracking
Why measuring a shop without cookies often delivers the more complete numbers.
- Data when banner is declinedOrders and revenue keep being captured since no tracking cookies are needed
- Setup in the shopOne script snippet; 25+ shop systems detected automatically
- Revenue & cart valueVisible directly, incl. orders, conversion rate and average order value
- Web Vitals of real shoppersLCP, CLS and INP from real visits, plus a Lighthouse run with performance-budget alerts
- Link with uptime & checkoutAnalytics, uptime and browser checks in one interface
- Data locationHosted in Germany, data stays in the EU, DPA under Art. 28
- Consent bannerFor plain reach and revenue measurement usually not required — assessment in each case is yours
- Custom eventsJS API for product view, cart, checkout step and order
- Data when banner is declinedPurchases that decline the banner are missing from the analysis
- Setup in the shopTag manager, conversion pixels and data-layer mapping per shop
- Revenue & cart valueOnly after pixel setup and often only for consenting visitors
- Web Vitals of real shoppersUsually a separate tool or pure lab measurement
- Link with uptime & checkoutSeparate subscriptions with their own logins and privacy reviews
- Data locationOften data flows to third countries with extra effort
- Consent bannerBanner usually required
- Custom eventsCustom events depending on plan and tag configuration
What XICTRAQ does for your shop
Downtime costs revenue
An unreachable shop sells nothing — while ad budget from running campaigns burns anyway. Three EU nodes check on a tight interval; an outage is reported only once several nodes confirm it.
Core Web Vitals as a conversion lever
Slow load times reduce conversion and can dampen Google visibility. LCP, CLS and INP are captured from real shopper visits; in addition, a regular Lighthouse run checks the website against a freely set performance budget.
Checkout & login with assertions
Browser monitoring clicks through the order path automatically and asserts that the confirmation text actually appears. If a step breaks, the alert arrives ahead of your customers, and a screenshot records the error state.
Measure revenue without cookies
Orders, revenue, cart value and conversion rate are captured cookieless — 25+ shop systems are detected automatically, with no data gaps from declined banners.
SSL & security for trust
An expired certificate or missing security headers scare buyers off at the moment of payment. SSL expiry, headers and known weaknesses are checked regularly, including an early warning before expiry.
SLA reports with MTTR
Monthly reports show availability, response time and the mean time to recovery (MTTR) per incident. That lets you prove to marketplaces, partners or management how stable the shop really runs.
Status page for your customers
During an incident a dedicated status page creates transparency instead of a wave of support tickets — with a custom domain and fully white-labelled on the Agency plan.
Auto-diagnosis on downtime
When the shop goes down, XICTRAQ automatically gathers context: HTTP status, DNS, SSL and the response times of the involved nodes. Instead of just "site gone" you see whether DNS, the certificate or the server itself is the cause.
Peak phases like Black Friday: prepare instead of hope
On high-revenue days the highest load and the most last-minute changes coincide — new promo banners, coupon logic, adjusted themes. That is precisely when the shop is most vulnerable and an outage most expensive. A short checklist helps: in the days before, shorten the check interval, deliberately tighten performance budgets, store a checkout browser check including a coupon-code step and double-check the SSL expiry warning so no certificate expires right in the campaign window.
So that a nighttime alert does not vanish into a silent inbox, escalation steps automatically pass an unacknowledged alert to the next person in the on-call schedule. If an outage becomes real anyway, the alert states the error the check saw, the auto-diagnosis records DNS, HTTP response and network path, and the SLA report afterwards documents availability and mean time to recovery (MTTR) for the follow-up with the team or the host.
After the peak phase the report becomes a decision aid: where did delays arise, which checkout step was slowest, did the performance budget hold up under the extra load? This analysis feeds into preparing the next campaign — turning a stressful day into a repeatable process.
Black Friday checklist
- Shorten the check interval in the days before
- Deliberately tighten performance budgets
- Store a checkout browser check including a coupon-code step
- Double-check the SSL expiry warning — no certificate should expire in the campaign window
- Enable escalation steps so nighttime alerts do not vanish
Frequently asked questions
How much revenue does an hour of downtime actually cost me?
A rough but honest rule of thumb: divide your monthly revenue by the number of hours during which purchases actually happen. A shop with 60,000 euros monthly revenue and sales spread over roughly twelve hours a day averages about 165 euros per hour — often a multiple of that during evening prime time. Paid ads keep running during the outage and land on an error page, so burned ad budget adds to the lost revenue. XICTRAQ does not shorten the outage itself, but the time until you know about it: the alert arrives as soon as several monitoring nodes confirm the issue.
Does XICTRAQ measure revenue and orders without cookies?
Yes. Shop analytics capture orders, revenue, cart value and conversion rate cookieless. No tracking cookies are set and nothing is stored in the browser; visits are told apart by a pseudonymous daily identifier that can no longer be attributed to an IP address once the day is over. A consent banner is therefore usually not required for reach and revenue measurement. The exception is automatic customer recognition from the Business plan: it links visits of logged-in customers to their customer number and, where the site provides them, to name or company, and is therefore personal data. The legal assessment in each case remains with you. More than 25 shop systems such as WooCommerce, Shopify, Shopware, Magento, PrestaShop or JTL are detected automatically.
What do assertions mean in checkout monitoring?
An assertion is a check condition that must hold after each step. Browser monitoring adds a product to the cart and then asserts the cart counter shows 1; after "place order" it asserts the text "Thank you for your order" is visible. These assertions turn a click path into a real functional test: a page can respond with status 200 and still fail to complete checkout. If a condition fails or a step takes too long, an alert fires and a screenshot of the error state is stored.
Do Core Web Vitals really help conversion and ranking?
Load time and visual stability affect how many visitors stay through to purchase, and they are among the signals Google uses for ranking. XICTRAQ measures LCP, CLS and INP from real visits rather than only in the lab; in addition, the regular Lighthouse run of the website can alert against a freely defined performance budget as soon as values deteriorate after a theme update, a new marketing script or a heavy banner. That way you see the cause before conversion visibly drops.
Does this work during Black Friday and peak phases too?
That is exactly when it pays off. During peak phases the shop becomes especially fragile due to load spikes, last-minute theme tweaks and new campaign scripts. It makes sense to shorten the check interval in the preceding days, deliberately tighten performance budgets and store a checkout browser check including a coupon-code step. Escalation steps ensure an unacknowledged alert is passed to the next person instead of going unnoticed overnight. In an emergency the alert states the error the check saw, such as an expired certificate, and the auto-diagnosis records DNS resolution, HTTP response and network path.
When is browser monitoring worth it on top of the uptime check?
The uptime check answers "does the server respond?", browser monitoring answers "can a customer actually order?". As soon as the order path depends on external services — payment provider, shipping plugin, login via a customer account — plain reachability is no longer enough. Rule of thumb: every critical path whose failure directly costs revenue belongs in a browser check with assertions. For purely static landing pages the uptime check usually suffices.
Does the analytics snippet slow down my shop?
The tracker snippet is loaded with "defer", kept small and does not block page rendering. Because it is served first-party via your own or the XICTRAQ domain, an extra third-party connection setup is avoided. The Web Vitals measurement itself runs passively in the background and does not noticeably affect the measured values — it reflects the real experience of your shoppers.
Do I still need separate tools alongside XICTRAQ?
For a typical online shop, XICTRAQ covers uptime and browser monitoring, SSL and security checks, SEO visibility, cookieless analytics including shop metrics, plus a status page and SLA reports in one platform — 21 modules, one interface, one invoice. That replaces several separate subscriptions with split logins and separate privacy reviews.
Where is the data processed?
XICTRAQ is hosted in Germany and the data stays within the EU. The three monitoring nodes are in Nuremberg, Helsinki and Falkenstein — Helsinki is in Finland and therefore in the EU. A data processing agreement (DPA) under Art. 28 GDPR is provided. The legal assessment of the processing in each case remains with you.
What does XICTRAQ cost for a shop?
There is a permanently free plan for one website, ideal for trying it out. Paid plans start at 12 euros per month, cancel monthly, and unlock more monitors, browser checks, analytics volume and white-label depending on the tier. No credit card is needed to start.
Monitoring per shop system
What typically breaks on your shop system, how XICTRAQ recognises it and which shop events the tracker captures there on its own.
Monitor availability, checkout and revenue in one place
Permanently free plan for one website, no credit card needed. Paid plans from 12 euros per month, cancel monthly.