Website review, no card needed

cipriani.com logo

cipriani.com website review

Visit site (opens in a new tab)Reviewed 3 November 202628 issues · 79 checks

This review found 28 issues worth fixing on cipriani.com, 7 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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
1.8 s1.6 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.6 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
198 ms105 msMay 16Oct 31179 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026121 ms
May 23, 2026120 ms
May 30, 2026116 ms
Jun 6, 2026117 ms
Jun 13, 2026119 ms
Jun 20, 2026121 ms
Jun 27, 2026125 ms
Jul 4, 2026125 ms
Jul 11, 2026123 ms
Jul 18, 2026123 ms
Jul 25, 2026121 ms
Aug 1, 2026121 ms
Aug 8, 2026121 ms
Aug 15, 2026121 ms
Aug 22, 2026121 ms
Aug 29, 2026122 ms
Sep 5, 2026137 ms
Sep 12, 2026156 ms
Sep 19, 2026174 ms
Sep 26, 2026186 ms
Oct 3, 2026187 ms
Oct 10, 2026185 ms
Oct 17, 2026180 ms
Oct 24, 2026183 ms
Oct 31, 2026179 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 cipriani.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cipriani.com at 0.9 s0.9 s
  2. cipriani.com at 1.8 s1.8 s
  3. cipriani.com at 2.6 s2.6 s
  4. cipriani.com at 3.5 s3.5 s
  5. cipriani.com at 4.4 s4.4 s
  6. cipriani.com at 5.3 s5.3 s
  7. cipriani.com at 6.2 s6.2 s
  8. cipriani.com at 7.1 s7.1 s

Speed

9 to fix52
  • Reduce unused JavaScript

    2.0 s · 801 KiB

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

  • Main-thread work: 4.3 s

    A phone's processor spends 4.3 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Wix, Google Tag Manager and Facebook and others), adding 2.6 MB and 1.8 s of main-thread time.

  • Mobile performance score: 52

    52/100

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

  • Wix adds 813 ms

    813 ms

    Wix costs a phone 813 ms of main-thread work and 1.3 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.

  • Render-blocking requests

    750 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

  • Google Tag Manager adds 628 ms

    628 ms

    Google Tag Manager costs a phone 628 ms of main-thread work and 674 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.

  • 10 long tasks on the main thread

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

  • 2,141 HTML elements

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

  • Use efficient cache lifetimes

    210 KiB

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

  • Duplicated JavaScript

    150 ms · 33 KiB

    33 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    59 KiB

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

  • Reduce unused CSS

    41 KiB

    About 41 KiB of CSS is downloaded but never applied on this page.

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

1 checks passed
  • Server response: 27 ms

    27 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 8.6 s

    8.6 s

    Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “slider-1.jpg”.

  • Time to Interactive: 18.0 s

    18.0 s

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

  • Speed Index: 7.9 s

    7.9 s

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

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

    +50%

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

  • Total Blocking Time: 454 ms

    454 ms

    Scripts block taps and scrolling for 454 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

7 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: 1.9 s

    1.9 s

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

  • Real-user INP: 182 ms

    182 ms

    Real visitors wait 182 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: 1.4 s

    1.4 s

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

  • Real-user TTFB: 597 ms

    597 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 3.6 MB in 276 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 276 requests on a phone: scripts 2.2 MB (121), other files 979 KiB (128) and images 222 KiB (21). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    slider-2.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).

  • About 1.0 g of CO₂ per visit

    1.03 g

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

2 checks passed
  • 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

1 to fixGoogle 9598
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

4 to fixGoogle 10079
  • Title is long (146 characters)

    Your title is 146 characters, so Google will cut it off around 60: “Cipriani | To serve is first to love | Upscale Fine Italian Dining, Iconic Lounges, Exclu…”.

  • 6 H1 headlines

    There are 6 <h1> headlines (“Simply Italian Since 1931”, “Restaurants & Lounges” and “Cipriani's Hospitality”). One clear main headline is easier for people and search engines.

  • Meta description is long (169 characters)

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

  • Structured data has 1 problem

    Structured data found (Restaurant and WebSite) but with 1 problem, for example “ld+json block 3 is not valid JSON (Bad control character in string literal in JSON at position )”.

  • 128 internal links, 99 external

    The homepage links to 128 pages on cipriani.com and 99 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.cipriani.com/.

  • 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.cipriani.com/sitemap.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, sameAs (social profiles) and description; logo and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 15 pages without an H1

    https://www.cipriani.com/book-a-table, https://www.cipriani.com/restaurants-and-lounges, https://www.cipriani.com/cipriani-mexico-city, https://www.cipriani.com/cipriani-las-vegas, https://www.cipriani.com/cipriani-beverly-hills and https://www.cipriani.com/cipriani-downtown-miami and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

  • About 517 words of copy

    The homepage carries about 517 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “RESERVE A TABLE”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Reserve A Table”, “CIPRIANI FOOD E-SHOP” and “RESERVE A TABLE”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • 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

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (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.

  • 21 other companies contacted

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

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

Upkeep, stack and company

Stack

CMS
Wix
Framework
React
Analytics
Google Analytics
Hosting
Wix

Company

Founded
1931

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on cipriani.com, including 15 speed issues, 4 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