Website review, no card needed

3dpromo.cz logo

3dpromo.cz website review

Visit site (opens in a new tab)Reviewed 14 November 202638 issues · 79 checks

This review found 38 issues worth fixing on 3dpromo.cz, 13 of them high impact, across 79 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

Full-page screenshot of 3dpromo.cz (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 3dpromo.cz at 0.4 s0.4 s
  2. 3dpromo.cz at 0.8 s0.8 s
  3. 3dpromo.cz at 1.1 s1.1 s
  4. 3dpromo.cz at 1.5 s1.5 s
  5. 3dpromo.cz at 1.9 s1.9 s
  6. 3dpromo.cz at 2.3 s2.3 s
  7. 3dpromo.cz at 2.6 s2.6 s
  8. 3dpromo.cz at 3.0 s3.0 s

Speed

10 to fix73
  • Use efficient cache lifetimes

    1.3 s · 693 KiB

    43 files are served with short cache lifetimes, so returning visitors download them again (693 KiB).

  • Render-blocking requests

    1.6 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • Improve image delivery

    1.3 MB

    13 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 73

    73/100

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

  • Reduce unused JavaScript

    750 ms · 207 KiB

    About 207 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 117 KiB

    About 117 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 2 third-party services on the page

    2 third-party services load with your homepage (promotron.com and promotte.com), adding 1.9 MB and 44 ms of main-thread time.

  • 1,662 HTML elements

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

  • promotte.com adds 0 ms

    0 ms

    promotte.com costs a phone 0 ms of main-thread work and 1.2 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.

  • promotron.com adds 44 ms

    44 ms

    promotron.com costs a phone 44 ms of main-thread work and 704 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

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • 2 long tasks on the main thread

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

  • Minify JavaScript

    19 KiB

    19 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    10 KiB

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

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 135 ms of it running JavaScript. That is comfortably low.

  • Server response: 102 ms

    102 ms

    Your server sent the HTML in 102 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix70
  • Largest Contentful Paint: 5.8 s

    5.8 s

    Your 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 image “web_sitotisk-1.png”.

  • Time to Interactive: 6.0 s

    6.0 s

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

  • 29 images without width and height

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Speed Index: 3.8 s

    3.8 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.08

    0.08

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

  • Total Blocking Time: 3 ms

    3 ms

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

Images and page weight

5 to fix33
  • 2 images over 500 KB

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

  • 3 images far larger than shown

    1.0 MB

    3 images are downloaded at several times the size a phone draws them, for example 897da3ec-4dc0-4d0c-bb91-aa9b83b1749f.png at 4,573 px wide, shown at 350 px. Resized copies would save about 1.0 MB.

  • Page weight: 2.2 MB in 49 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 49 requests on a phone: images 1.5 MB (27), scripts 298 KiB (5) and fonts 296 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (1.3 MB) 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.

  • 3 images below the first screen load straight away

    3 images further down the page (578 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.63 g

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

Accessibility

5 to fixGoogle 9393
  • 8 tap targets too small

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

  • 3 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 240 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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

4 to fixGoogle 9265
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (16 characters)

    Your title is only 16 characters: “Homepage e-shopu”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 476 internal links, 4 external

    The homepage links to 476 pages on 3dpromo.cz and 4 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.3dpromo.cz/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.3dpromo.cz/sitemap.xml.

AI search readiness

1 to fix65
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

3 checks passed
  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (738 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.3dpromo.cz/llms.txt (2 KiB, 21 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.3dpromo.cz/cs/zpracovani-osobnich-udaju, https://www.3dpromo.cz/cs/psaci-potreby, https://www.3dpromo.cz/cs/pera, https://www.3dpromo.cz/cs/tuzky, https://www.3dpromo.cz/cs/rollery and https://www.3dpromo.cz/cs/zvyraznovace and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 11 small tap targets

    11 of 44 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

6 to fix56
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 218 words

    The homepage has only about 218 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 4 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 3dpromo.cz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on 3dpromo.cz, including 15 speed issues, 4 SEO issues and 6 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