Website review, no card needed
terd.at website review
Visit site (opens in a new tab)Reviewed 11 November 202633 issues · 80 checks
This review found 33 issues worth fixing on terd.at, 10 of them high impact, across 80 checks. The most urgent: main-thread work: 5.6 s. 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
77C- #57,164 of 101,676 reviewed websitesbeats 39%
- #36,266 of 56,329 online storesbeats 30%
- #34,472 of 51,212 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 144 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 152 ms |
| Jun 20, 2026 | 158 ms |
| Jun 27, 2026 | 163 ms |
| Jul 4, 2026 | 174 ms |
| Jul 11, 2026 | 181 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 195 ms |
| Aug 1, 2026 | 198 ms |
| Aug 8, 2026 | 205 ms |
| Aug 15, 2026 | 204 ms |
| Aug 22, 2026 | 188 ms |
| Aug 29, 2026 | 181 ms |
| Sep 5, 2026 | 182 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 173 ms |
| Sep 26, 2026 | 178 ms |
| Oct 3, 2026 | 173 ms |
| Oct 10, 2026 | 185 ms |
| Oct 17, 2026 | 195 ms |
| Oct 24, 2026 | 181 ms |
| Oct 31, 2026 | 177 ms |
| Nov 7, 2026 | 164 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
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
900 ms · 544 KiBAbout 544 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (incognia.com, iubenda and Google Tag Manager and others), adding 926 KiB and 1.3 s of main-thread time.
Use efficient cache lifetimes
650 ms · 458 KiB21 files are served with short cache lifetimes, so returning visitors download them again (458 KiB).
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
incognia.com adds 327 ms
327 msincognia.com costs a phone 327 ms of main-thread work and 228 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.
iubenda adds 296 ms
296 msiubenda costs a phone 296 ms of main-thread work and 121 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 292 ms. During a long task the page ignores taps.
Google Tag Manager adds 256 ms
256 msGoogle Tag Manager costs a phone 256 ms of main-thread work and 322 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
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.
1 checks passed
Server response: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 13.6 s
13.6 sThe page becomes fully interactive after 13.6 s. Good is under 3.8 s.
Largest Contentful Paint: 5.8 s
5.8 sYour largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Dein Gutschein in 5 Sekunden. Ergebnisse für”.
Total Blocking Time: 773 ms
773 msScripts block taps and scrolling for 773 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 144 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.5 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.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: 93 ms
93 msReal visitors wait 93 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 356 ms
356 msReal visitors wait 356 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
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.
Images and page weight
Page weight: 3.3 MB in 377 requests
3.3 MBYour homepage downloads 3.3 MB in 377 requests on a phone: scripts 1.5 MB (63), other files 1.4 MB (289) and images 162 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
22 form fields without a label
22 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“<div class="logo__image-wrapper"> <img src="//ter…” and “Dein Gutschein in 5 Sekunden.”). One clear main headline is easier for people and search engines.
53 internal links, 6 external
The homepage links to 53 pages on terd.at and 6 external pages.
6 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Prepaidkarten und Guthabenkarten jeglicher Art einfach online kaufen. Zum Guthaben aufladen oder als Geschenkgutschein.…”.
Title: 54 characters
Your title is a healthy 54 characters: “Terd | Gutscheine und Guthaben Online kaufen – Terd.at”.
Canonical URL set
The canonical URL is https://terd.at/.
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://terd.at/sitemap.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (910 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://terd.at/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 linked pages hidden from search
https://terd.at/products/paysafecard-100, https://terd.at/products/paysafecard-25, https://terd.at/products/paysafecard-50, https://terd.at/products/paysafecard-10 and https://terd.at/products/paysafecard-flex are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://terd.at/collections/rewarble and https://terd.at/products/rewarble-flex-1 all use the title “Rewarble – Terd.at”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://terd.at/collections/rewarble has no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://terd.at/products/paysafecard-100, https://terd.at/products/paysafecard-25, https://terd.at/products/paysafecard-50, https://terd.at/products/paysafecard-10 and https://terd.at/products/paysafecard-flex 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 33 found) and read each the way a search engine does.
3 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 title
All 15 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://terd.at/.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot set properties of null (setting 'api_endpoint')”.
Requests the notification permission on page load
Requests the notification permission on page load.
2 checks passed
Tap targets are thumb-sized
22 of 23 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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 247 words
The homepage has only about 247 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
25 short forms
25 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 1 of them by other companies (measured from a US location before any click).
37 other companies contacted
Loading the homepage contacts 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: iubenda
A consent management tool (iubenda) 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 terd.at, 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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Complianz Consent · Minmaxify Order Limits · Omnisend · pushowl.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 33 issues on terd.at, including 13 speed issues, 2 SEO issues and 5 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.