Programmable

Website review, no card needed

moris.cz logo

moris.cz website review

Visit site (opens in a new tab)Reviewed 19 October 202622 issues · 75 checks

This review found 22 issues worth fixing on moris.cz, 7 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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

Site score

84B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
923 ms619 msMay 2Oct 17685 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026654 ms
May 9, 2026710 ms
May 16, 2026787 ms
May 23, 2026801 ms
May 30, 2026888 ms
Jun 6, 2026813 ms
Jun 13, 2026776 ms
Jun 20, 2026749 ms
Jun 27, 2026698 ms
Jul 4, 2026801 ms
Jul 11, 2026696 ms
Jul 18, 2026741 ms
Jul 25, 2026796 ms
Aug 1, 2026793 ms
Aug 8, 2026835 ms
Aug 15, 2026768 ms
Aug 22, 2026744 ms
Aug 29, 2026777 ms
Sep 5, 2026734 ms
Sep 12, 2026827 ms
Sep 19, 2026849 ms
Sep 26, 2026701 ms
Oct 3, 2026779 ms
Oct 10, 2026711 ms
Oct 17, 2026685 ms
Real-visitor tap response (INP)75th percentile, phones
209 ms95 msMay 2Oct 17108 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026113 ms
May 9, 2026121 ms
May 16, 2026134 ms
May 23, 2026144 ms
May 30, 2026196 ms
Jun 6, 2026172 ms
Jun 13, 2026135 ms
Jun 20, 2026121 ms
Jun 27, 2026110 ms
Jul 4, 2026111 ms
Jul 18, 2026109 ms
Aug 22, 2026127 ms
Aug 29, 2026123 ms
Sep 5, 2026112 ms
Sep 12, 2026120 ms
Sep 19, 2026118 ms
Sep 26, 2026116 ms
Oct 3, 2026116 ms
Oct 10, 2026111 ms
Oct 17, 2026108 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

moris.cz (opens in a new tab)
Full-page screenshot of moris.cz (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix71

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 71

    71/100

    Your mobile performance score is 71 (desktop: 88). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    150 ms · 35 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (mysuitu.com and Google Fonts), adding 151 KiB and 43 ms of main-thread time.

  • Improve image delivery

    24 KiB

    3 images could be 24 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

  • Server response: 114 ms

    114 ms

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

Core Web Vitals

5 to fix100

  • Largest Contentful Paint: 6.1 s

    6.1 s

    Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Time to Interactive: 6.2 s

    6.2 s

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

  • Speed Index: 4.6 s

    4.6 s

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.7 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: 0.7 s

    0.7 s

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

  • Real-user INP: 108 ms

    108 ms

    Real visitors wait 108 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: 0.5 s

    0.5 s

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

  • Real-user TTFB: 240 ms

    240 ms

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

  • Cumulative Layout Shift: 0.012

    0.012

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100

  • 1 image below the first screen load straight away

    1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.2 g of CO₂ per visit

    0.20 g

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

3 checks passed

  • Page weight: 717 KiB in 62 requests

    717 KiB

    Your homepage downloads 717 KiB in 62 requests on a phone: images 527 KiB (29), scripts 91 KiB (11) and fonts 46 KiB (6). That is a lean page.

  • 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

4 to fixGoogle 7891

  • Hidden but focusable

    9 elements hidden from screen readers can still receive keyboard focus.

  • 31 images without alt text

    31 images have no alt text, which hurts accessibility and image search.

  • 127 links without text

    127 visible links have no text or label, so screen readers cannot say where they go.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 checks passed

  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 7777

  • No meta description

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

  • Title is short (8 characters)

    Your title is only 8 characters: “Moris.cz”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • 16 links with vague text

    16 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

  • 93 internal links, 40 external

    The homepage links to 93 pages on moris.cz and 40 external pages.

5 checks passed

  • One H1 headline

    Your main headline reads: “We create spaces that sell”.

  • Canonical URL set

    The canonical URL is https://moris.cz/en/.

  • Structured data in place

    Structured data found: Corporation, Organization, ProfessionalService, WebApplication and WebPage.

  • 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://moris.cz/sitemap.xml.

AI search readiness

100

  • No llms.txt

    There is no https://moris.cz/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, sameAs (social profiles) and contact details; logo and description would complete it.

  • Text is in the HTML

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

Other pages

2 to fix88

  • 4 pages share a title

    https://moris.cz/en, https://moris.cz/cs, https://moris.cz/de and https://moris.cz/pl all use the title “Moris.cz”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://moris.cz/en/references, https://moris.cz/en/about-us, https://moris.cz/en/services, https://moris.cz/en/news, https://moris.cz/en/showroom and https://moris.cz/en/contact and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://moris.cz/en/showroom has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 53 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.

  • 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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.mysuitu.com/plugins/normalize.min.css' from origin 'https://moris.cz' has been…”.

2 checks passed

  • Tap targets are thumb-sized

    129 of 129 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69

  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • No opening hours

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

  • 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 434 words of copy

    The homepage carries about 434 words of visible text.

5 checks passed

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”, “Non-binding request” and “For download”.

  • 1 short form

    A short form (6 fields at most) is right on the homepage, asking for an email.

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

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

  • 3 other companies contacted

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

Upkeep, stack and company

Stack

CMS
MySUITU CMS
Framework
jQuery

Company

Founded
1997
Headquarters
Prague

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on moris.cz, including 7 speed issues, 5 SEO issues and 3 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