svn.com website review

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

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

About 1.2 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.3 s faster on a phone.

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

5 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

8 third-party services load with your homepage (buildout.com, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 2.1 MB and 1.0 s of main-thread time.

buildout.com costs a phone 370 ms of main-thread work and 586 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.

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

77 KiB could be saved by minifying CSS.

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

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

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

148 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SVN® delivers commercial real estate services that accelera…”.

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

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

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

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

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

2 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-31, real Chrome visitors' tap response (inp) went from 126 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 18.8 MB in 128 requests on a phone: images 11.4 MB (33), media 3.6 MB (2) and scripts 2.0 MB (36). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (337 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (311 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.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 75 characters, so Google will cut it off around 60: “Commercial Real Estate Properties, Services & Advisors - SVN® International”.

The homepage links to 73 pages on svn.com and 5 external pages.

https://svn.com/commercial-property-types/office-commercial-real-estate, https://svn.com/commercial-property-types/retail-commercial-real-estate, https://svn.com/commercial-property-types/commercial-land-for-sale, https://svn.com/commercial-property-types/single-tenant-property-investment, https://svn.com/commercial-property-types/hospitality-commercial-real-estate and https://svn.com/commercial-property-types/healthcare-real-estate-brokers and 3 others took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your longest form asks for 16 fields (0 required). Every extra field lowers completion.

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

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

The homepage carries about 661 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

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.

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