Website review, no card needed

circulee.com logo

circulee.com website review

Visit site (opens in a new tab)Reviewed 22 November 202639 issues · 84 checks

This review found 39 issues worth fixing on circulee.com, 21 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.7 s1.7 sMay 30Nov 142.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.5 s
Jun 6, 20263.4 s
Jun 13, 20263.0 s
Jun 20, 20262.7 s
Jun 27, 20262.6 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20262.1 s
Oct 31, 20262.2 s
Nov 7, 20262.2 s
Nov 14, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
177 ms115 msMay 30Nov 14170 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026129 ms
Jun 6, 2026122 ms
Jun 13, 2026138 ms
Jun 20, 2026146 ms
Jun 27, 2026153 ms
Jul 4, 2026158 ms
Jul 11, 2026163 ms
Jul 18, 2026158 ms
Jul 25, 2026155 ms
Aug 1, 2026157 ms
Aug 8, 2026152 ms
Aug 15, 2026161 ms
Aug 22, 2026168 ms
Aug 29, 2026162 ms
Sep 5, 2026168 ms
Sep 12, 2026158 ms
Sep 19, 2026153 ms
Sep 26, 2026158 ms
Oct 3, 2026151 ms
Oct 10, 2026150 ms
Oct 17, 2026153 ms
Oct 24, 2026157 ms
Oct 31, 2026165 ms
Nov 7, 2026169 ms
Nov 14, 2026170 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

Full-page screenshot of circulee.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. circulee.com at 1.5 s1.5 s
  2. circulee.com at 2.9 s2.9 s
  3. circulee.com at 4.4 s4.4 s
  4. circulee.com at 5.8 s5.8 s
  5. circulee.com at 7.3 s7.3 s
  6. circulee.com at 8.7 s8.7 s
  7. circulee.com at 10.2 s10.2 s
  8. circulee.com at 11.6 s11.6 s

Speed

10 to fix60
  • Use efficient cache lifetimes

    1.2 s · 11.3 MB

    24 files are served with short cache lifetimes, so returning visitors download them again (11.3 MB).

  • Improve image delivery

    1.1 s · 9.8 MB

    15 images could be 9.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Document request latency

    2.1 s

    The HTML itself could arrive about 2.1 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    2.1 s

    Reduce initial server response time. Google estimates savings of 2.1 s on a phone.

  • Reduce unused JavaScript

    1.5 s · 441 KiB

    About 441 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Server response: 2.2 s

    2.2 s

    Your server takes 2.2 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 304 ms

    304 ms

    Google Tag Manager costs a phone 304 ms of main-thread work and 502 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,532 HTML elements

    The page has 2,532 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Main-thread work: 2.1 s

    A phone's processor spends 2.1 s on main-thread work while loading, 945 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Usercentrics CMP and Shopify and others), adding 760 KiB and 426 ms of main-thread time.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    28 KiB

    About 28 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 9.3 s

    9.3 s

    Your largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Refurbished Hardware für Unternehmen”.

  • Speed Index: 12.2 s

    12.2 s

    Visually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 13.0 s

    13.0 s

    The page becomes fully interactive after 13.0 s. Good is under 3.8 s.

  • Tap response (INP) got 35% slower for real visitors

    +35%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 129 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

  • 11 images without width and height

    11 images have no width and height attributes, so the layout jumps as each one loads.

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: 2.1 s

    2.1 s

    Real visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 162 ms

    162 ms

    Real visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 581 ms

    581 ms

    Real visitors wait 581 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 37% faster for real visitors

    -37%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.5 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 161 ms

    161 ms

    Scripts block the page for only 161 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

Images and page weight

5 to fix29
  • Page weight: 13.5 MB in 104 requests

    13.5 MB

    Your homepage downloads 13.5 MB in 104 requests on a phone: images 11.3 MB (28), scripts 1.3 MB (49) and HTML 373 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 8.9 MB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    4.8 MB

    12 images are downloaded at several times the size a phone draws them, for example video-cover-v2.webp at 1,280 px wide, shown at 334 px. Resized copies would save about 4.8 MB.

  • 10 images below the first screen load straight away

    10 images further down the page (9.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    main.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).

  • 6 images in older formats

    6 images (268 KiB) 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 3.8 g of CO₂ per visit

    3.82 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.82 g of CO₂e: 458.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

7 to fixGoogle 7888
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 23 tap targets too small

    23 tap targets are too small or too close together to hit reliably with a finger.

  • Links must have discernible text (4 elements)

    Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 40 images in the HTML carry an alt attribute.

  • 45 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: 45 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10092
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 48 internal links, 17 external

    The homepage links to 48 pages on circulee.com and 17 external pages.

6 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Statte Dein Team mit hochwertiger, aufbereiteter Hardware aus ✓ spart bis zu 50 % Kosten ✓ spart bis zu 80% CO₂ ✓ 12 Mo…”.

  • One H1 headline

    Your main headline reads: “Erstklassige, gebrauchte Hardware für Dein Business”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Erstklassige, gebrauchte Hardware für Dein Business | circulee”.

  • Canonical URL set

    The canonical URL is https://www.circulee.com/.

  • 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.circulee.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.circulee.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.

2 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 (1,243 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix80
  • 1 page without a title

    https://www.circulee.com/products/bestsellers has no <title>, so Google invents the link text in results.

  • 3 pages without a meta description

    https://www.circulee.com/products/bestsellers, https://www.circulee.com/pc-zubehoer and https://www.circulee.com/services/end-of-life have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages slow to respond

    https://www.circulee.com/services/end-of-life and https://www.circulee.com/products/hp-elite-book-830-g8-13%2C3''-intel-core-i5-1145g7-16gb-ram-256gb-ssd-fhd-win11-pro--sk--lap-hpx-e830g8-0003-de took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.

5 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.

  • 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.

Best practices

1 to fixGoogle 9693
  • 6 small tap targets

    6 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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: 3 trust badges. 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 1,127 words of copy

    The homepage carries about 1,127 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

  • 7 other companies contacted

    Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) 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 circulee.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

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
Next.js
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on circulee.com, including 16 speed issues, 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25