Website review, no card needed

san-marco.com logo

san-marco.com website review

Visit site (opens in a new tab)Reviewed 17 November 202650 issues · 94 checks

This review found 50 issues worth fixing on san-marco.com, 17 of them high impact, across 94 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
5.3 s3.3 sMay 30Nov 144.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.6 s
Jun 6, 20263.6 s
Jun 13, 20263.8 s
Jun 20, 20264.1 s
Jun 27, 20264.3 s
Jul 4, 20264.5 s
Jul 11, 20264.3 s
Jul 18, 20264.1 s
Jul 25, 20263.8 s
Aug 1, 20263.7 s
Aug 8, 20263.6 s
Aug 15, 20263.6 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.9 s
Oct 3, 20264.3 s
Oct 10, 20264.6 s
Oct 17, 20264.9 s
Oct 24, 20265.1 s
Oct 31, 20265.1 s
Nov 7, 20264.9 s
Nov 14, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
294 ms210 msMay 30Nov 14262 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026220 ms
Jun 6, 2026221 ms
Jun 13, 2026225 ms
Jun 20, 2026230 ms
Jun 27, 2026235 ms
Jul 4, 2026238 ms
Jul 11, 2026237 ms
Jul 18, 2026234 ms
Jul 25, 2026235 ms
Aug 1, 2026232 ms
Aug 8, 2026235 ms
Aug 15, 2026239 ms
Aug 22, 2026241 ms
Aug 29, 2026241 ms
Sep 5, 2026238 ms
Sep 12, 2026235 ms
Sep 19, 2026231 ms
Sep 26, 2026235 ms
Oct 3, 2026250 ms
Oct 10, 2026264 ms
Oct 17, 2026276 ms
Oct 24, 2026284 ms
Oct 31, 2026279 ms
Nov 7, 2026272 ms
Nov 14, 2026262 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 san-marco.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. san-marco.com at 0.5 s0.5 s
  2. san-marco.com at 1.0 s1.0 s
  3. san-marco.com at 1.5 s1.5 s
  4. san-marco.com at 2.1 s2.1 s
  5. san-marco.com at 2.6 s2.6 s
  6. san-marco.com at 3.1 s3.1 s
  7. san-marco.com at 3.6 s3.6 s
  8. san-marco.com at 4.1 s4.1 s

Speed

13 to fix54
  • Use efficient cache lifetimes

    4.1 s · 540 KiB

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

  • Render-blocking requests

    2.5 s

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

  • Reduce unused JavaScript

    1.8 s · 583 KiB

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

  • Improve image delivery

    650 ms · 1.1 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Clarity and Google Tag Manager and others), adding 5.6 MB and 433 ms of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • Document request latency

    750 ms

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

  • Reduce initial server response time

    739 ms

    Reduce initial server response time. Google estimates savings of 739 ms on a phone.

  • storeden.net adds 38 ms

    38 ms

    storeden.net costs a phone 38 ms of main-thread work and 4.7 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.

  • Minify JavaScript

    300 ms · 45 KiB

    45 KiB could be saved by minifying JavaScript.

  • 2,456 HTML elements

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

  • Google CDN adds 91 ms

    91 ms

    Google CDN costs a phone 91 ms of main-thread work and 352 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.

  • Server response: 839 ms

    839 ms

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

  • Reduce unused CSS

    150 ms · 69 KiB

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

  • 8 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    25 KiB

    Polyfills for old browsers add 25 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.

1 checks passed
  • Main-thread work: 1.9 s

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

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 13.6 s

    13.6 s

    Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Decora la tua casa con San Marco”.

  • Time to Interactive: 17.0 s

    17.0 s

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

  • First Contentful Paint: 5.1 s

    5.1 s

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

  • Speed Index: 9.8 s

    9.8 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user INP: 212 ms

    212 ms

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

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

    +21%

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

  • Largest content (LCP) got 32% slower for real visitors

    +32%

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • 25 images without width and height

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

4 checks passed
  • 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 TTFB: 699 ms

    699 ms

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

  • Total Blocking Time: 192 ms

    192 ms

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

  • Cumulative Layout Shift: 0.011

    0.011

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

Images and page weight

5 to fix18
  • Page weight: 6.3 MB in 117 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 117 requests on a phone: images 4.6 MB (60), scripts 1.4 MB (28) and fonts 216 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    69cb99ce202628515ff4aa70 weighs 1.3 MB. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    700 KiB

    6 images are downloaded at several times the size a phone draws them, for example 6aeb6220be7ea0412e596e0c at 944 px wide, shown at 276 px. Resized copies would save about 700 KiB.

  • 32 images in older formats

    32 images (4.4 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.

  • 13 images below the first screen load straight away

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

  • About 1.8 g of CO₂ per visit

    1.80 g

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

Accessibility

9 to fixGoogle 7488
  • Certain ARIA roles must contain particular children (3 elements)

    Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

  • 8 text elements with low contrast

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

  • ARIA input fields must have an accessible name (3 elements)

    ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

  • 41 images without alt text

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

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

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

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

  • 8 form fields without a label

    8 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 4 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

1 checks passed
  • 44 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: 44 passed and 10 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 9287
  • 7 H1 headlines

    There are 7 <h1> headlines (“Decora la tua casa conSan Marco”, “Allover Smalto” and “Pronti oggiper i cantieri di domani”). One clear main headline is easier for people and search engines.

  • Meta description is long (190 characters)

    Your meta description is 190 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 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 X (Twitter) card tag

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

  • 167 internal links, 24 external

    The homepage links to 167 pages on san-marco.com and 24 external pages.

5 checks passed
  • Title: 58 characters

    Your title is a healthy 58 characters: “San Marco | Pitture e Vernici per l'Edilizia Professionale”.

  • Canonical URL set

    The canonical URL is https://san-marco.com/.

  • Structured data in place

    Structured data found: WebSite.

  • 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://san-marco.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://san-marco.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,551 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://san-marco.com/pitture-sostenibili-per-ambiente has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://san-marco.com/pitture-sostenibili-per-ambiente, https://san-marco.com/stucchi-colle-premiscelati and https://san-marco.com/diluenti have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://san-marco.com/idropitture-e-smalti-murali, https://san-marco.com/rivestimenti-murali, https://san-marco.com/pitture-antimuffa, https://san-marco.com/smalti-e-prodotti-di-fondo, https://san-marco.com/stucchi-colle-premiscelati and https://san-marco.com/diluenti took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7376
  • 1 broken image

    1 image failed to load on a phone, for example https://newpim.san-marco.com/SMG/ZZ-Extra/Color%20Trends%202027/landing-page-colortrends-2027-mobile.jpg.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.storeden.net/themes/blomming/bootstrap4/css/bootstrap.min.css' from origin 'ht…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 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 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 831 words of copy

    The homepage carries about 831 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Reference book”, “Area Download” and “Download”.

  • 1 short form

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

  • Social proof on the page

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

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • 24 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

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

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
Momit Momit Srl

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on san-marco.com, including 24 speed issues, 3 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