fornarina.com website review

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

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

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

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

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

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

7 third-party services load with your homepage (Facebook, Google Tag Manager and iubenda and others), adding 670 KiB and 407 ms of main-thread time.

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

30 KiB could be saved by minifying JavaScript.

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

Desktop scores 94 but mobile only 65. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 6.3 MB in 93 requests on a phone: images 4.8 MB (28), scripts 1,005 KiB (36) and fonts 450 KiB (4). Under 2 MB keeps phones on slow connections fast.

3 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.

5 images (2.7 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.

Slide-Home.jpg 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).

1 image is downloaded at several times the size a phone draws it, for example Slide-Home.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 423 KiB.

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

Image buttons must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

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

Your title is only 18 characters: “Fornarina Official”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 66 characters: “Everyday we say no to limits and boundaries | New Shoes Collection”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Structured data found (Organization, WebPage and WebSite) but with 2 problems, for example “WebSite: missing name”.

No XML sitemap at https://www.fornarina.com/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 49 pages on fornarina.com and 14 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

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, which the crawlers above handle.

Your homepage links to //module/iqitwishlist/view, which answers with an error. Visitors hit a dead end and search engines drop it.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-images.mailchimp.com/embedcode/classic-071822.css' from origin 'https://www.fo…”.

3 images are served at too low a resolution for sharp phone screens.

1 link from your homepage to your own site is broken, for example https://www.fornarina.com//module/iqitwishlist/view (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://fornarina.com goes through 2 redirects before the homepage loads.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

fornarina.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

fornarina.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

fornarina.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

DMARC is set to p=none, so mail pretending to be fornarina.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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