Website review, no card needed
1423florestaplace.com website review
Visit site (opens in a new tab)Reviewed 9 November 202632 issues · 68 checks
This review found 32 issues worth fixing on 1423florestaplace.com, 12 of them high impact, across 68 checks. The most urgent: page weight: 49.0 MB in 166 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
66DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 third-party services on the page
6 third-party services load with your homepage (leadconnectorhq.com, cloudflare.com and elfsightcdn.com and others), adding 47.2 MB and 213 ms of main-thread time.
filesafe.space adds 0 ms
0 msfilesafe.space costs a phone 0 ms of main-thread work and 45.1 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.
Reduce unused JavaScript
750 ms · 137 KiBAbout 137 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
leadconnectorhq.com adds 144 ms
144 msleadconnectorhq.com costs a phone 144 ms of main-thread work and 1.9 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.
2,961 HTML elements
The page has 2,961 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
250 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
Reduce unused CSS
150 ms · 54 KiBAbout 54 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.
Improve image delivery
150 ms · 49 KiB4 images could be 49 KiB 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 143 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
15 KiB4 files are served with short cache lifetimes, so returning visitors download them again (15 KiB).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
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.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 704 ms of it running JavaScript. That is comfortably low.
Server response: 47 ms
47 msYour server sent the HTML in 47 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 160.7 s
160.7 sYour largest element takes 160.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 169.1 s
169.1 sThe page becomes fully interactive after 169.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.585
0.585The layout shifts by 0.585 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Speed Index: 4.2 s
4.2 sVisually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 206 ms
206 msScripts block taps and scrolling for 206 ms in total while the page loads. Good is under 200 ms.
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.
Images and page weight
Page weight: 49.0 MB in 166 requests
49.0 MBYour homepage downloads 49.0 MB in 166 requests on a phone: images 46.3 MB (69), other files 1.4 MB (16) and scripts 531 KiB (57). Under 2 MB keeps phones on slow connections fast.
14 images over 500 KB
14 images weigh 39.6 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
3.8 MB6 images are downloaded at several times the size a phone draws them, for example 6a57bfe1c06d2134c6c7f3fb.png at 1,086 px wide, shown at 320 px. Resized copies would save about 3.8 MB.
40 images in older formats
40 images (44.6 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.
6 images below the first screen load straight away
6 images further down the page (8.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 13.9 g of CO₂ per visit
13.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 13.90 g of CO₂e: 1667.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
42 images without alt text
42 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (52 elements)
All page content should be contained by landmarks: 52 elements on the page fail this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
39 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: 39 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
110 H1 headlines
There are 110 <h1> headlines (“LV Privé | Property Curation & Presentation 1423 …”, “1423 FLORESTA PLACE” and “Managed by LV Privé”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Only 4 internal links
The homepage links to only 4 pages on your own site, so visitors and crawlers find few routes into the rest of it.
5 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “Discover a luxury 7-bedroom Mediterranean estate with ocean views, wellness sanctuary, pool, spa, and smart home in Pac…”.
Title: 64 characters
Your title is a healthy 64 characters: “1423 Floresta | Luxury Mediterranean Estate in Pacific Palisades”.
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.
XML sitemap found
Your XML sitemap is reachable at https://1423florestaplace.com/sitemap.xml.
AI search readiness
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://1423florestaplace.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 (3,144 words), so crawlers that don't run JavaScript still read it.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 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 2,692 words of copy
The homepage carries about 2,692 words of visible text.
5 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Schedule a Viewing”, “Book Long-Term on Zillow” and “Book via VRBO”.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, a star rating and 35 trust badges.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 3 of them by other companies (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.
10 other companies contacted
Loading the homepage contacts 10 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 1423florestaplace.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on 1423florestaplace.com, including 12 speed issues, 4 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.