Programmable

Website review, no card needed

morolabs.it logo

morolabs.it website review

Visit site (opens in a new tab)Reviewed 11 November 202626 issues · 70 checks

This review found 26 issues worth fixing on morolabs.it, 12 of them high impact, across 70 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

Site score

70C

Closest competitors among reviewed websites

Compare side by side

One score from every part of this review. How it works

www.morolabs.it (opens in a new tab)
Full-page screenshot of morolabs.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. morolabs.it at 0.7 s0.7 s
  2. morolabs.it at 1.4 s1.4 s
  3. morolabs.it at 2.1 s2.1 s
  4. morolabs.it at 2.8 s2.8 s
  5. morolabs.it at 3.5 s3.5 s
  6. morolabs.it at 4.2 s4.2 s
  7. morolabs.it at 4.9 s4.9 s
  8. morolabs.it at 5.6 s5.6 s

Speed

6 to fix46

  • Use efficient cache lifetimes

    6.3 s · 1.3 MB

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

  • Reduce unused JavaScript

    1.6 s · 329 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 46

    46/100

    Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused CSS

    600 ms · 109 KiB

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

  • Improve image delivery

    450 ms · 65 KiB

    3 images could be 65 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 2 long tasks on the main thread

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

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

2 checks passed

  • Main-thread work: 1.4 s

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

  • Server response: 199 ms

    199 ms

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

Core Web Vitals

4 to fix40

  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sicurezza IT Protezione dati Conformità Innovazione SERVIZI…”. Most of its time is resource load delay (3.2 s).

  • Cumulative Layout Shift: 0.549

    0.549

    The layout shifts by 0.549 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 8.7 s

    8.7 s

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

  • Time to Interactive: 6.9 s

    6.9 s

    The page becomes fully interactive after 6.9 s. Good is under 3.8 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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 60 ms

    60 ms

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

Images and page weight

100

  • 2 images in older formats

    2 images (137 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 0.4 g of CO₂ per visit

    0.37 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.37 g of CO₂e: 45.0 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: 1.3 MB in 86 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 86 requests on a phone: images 474 KiB (11), scripts 459 KiB (7) and fonts 220 KiB (7). That is a lean page.

  • 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

4 to fixGoogle 8893

  • 12 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • All page content should be contained by landmarks (10 elements)

    All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.

  • 2 links without text

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

  • Headings skip levels

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

2 checks passed

  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

1 to fixGoogle 10093

  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “morolabs - Sicurezza IT Protezione dati personali Conformità Innovazione”.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 29 internal links, 1 external

    The homepage links to 29 pages on morolabs.it and 1 external page.

7 checks passed

  • Meta description: 130 characters

    Your meta description is 130 characters: “Sicurezza IT (NIS2 ISO/IEC 27001 ISO 22301 CIS v8) Protezione dati personali (GDPR) Conformità (ISO 37001 Modello 231) …”.

  • One H1 headline

    Your main headline reads: “Sicurezza IT Protezione dati Conformità Innovazione”.

  • Canonical URL set

    The canonical URL is https://www.morolabs.it/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://www.morolabs.it/sitemap_index.xml.

AI search readiness

100
4 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, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.morolabs.it/llms.txt (1 KiB, 1 link), a plain-text guide to the site for AI tools.

Other pages

6 to fix62

  • 1 page without a title

    https://www.morolabs.it/index.php/conformita has no <title>, so Google invents the link text in results.

  • 4 pages share 2 titles

    https://www.morolabs.it/solutions and https://www.morolabs.it/index.php/solutions all use the title “Servizi e Soluzioni - morolabs Sicurezza IT Protezione dati Conformit…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.morolabs.it/author/info_i094rsns and https://www.morolabs.it/index.php/conformita have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages share a meta description

    https://www.morolabs.it/solutions, https://www.morolabs.it/direttiva-nis2, https://www.morolabs.it/faq, https://www.morolabs.it/get-started, https://www.morolabs.it/index.php/solutions and https://www.morolabs.it/index.php/servizi-rpd-dpo and 4 others use the same meta description. A description written for each page earns more clicks.

  • 6 links to non-canonical URLs

    Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.morolabs.it/index.php/solutions, whose canonical is https://www.morolabs.it/solutions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 12 pages without an H1

    https://www.morolabs.it/about-morolabs-massima-sicurezza-conformita, https://www.morolabs.it/solutions, https://www.morolabs.it/faq, https://www.morolabs.it/get-started, https://www.morolabs.it/index.php/solutions and https://www.morolabs.it/index.php/servizi-rpd-dpo and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.morolabs.it/faq and https://www.morolabs.it/author/info_i094rsns have 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.

  • 8 pages slow to respond

    https://www.morolabs.it/sql2app-sviluppo-applicazioni-web-pwa-no-low-full-code, https://www.morolabs.it/faq, https://www.morolabs.it/get-started, https://www.morolabs.it/author/info_i094rsns, https://www.morolabs.it/index.php/servizi-rpd-dpo and https://www.morolabs.it/index.php/sicurezza-it and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 10093

  • 17 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

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.

  • No analytics detected

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

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

    The homepage carries about 531 words of visible text.

1 checks passed

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.

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.

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
Aruba S.p.A.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on morolabs.it, including 10 speed issues, 1 SEO issue 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