reit.com website review

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

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

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

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

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

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

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

The page goes through 1 redirect before it starts loading, costing about 780 ms. Link and advertise the final URL directly.

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

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

3 images could be 193 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

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 19.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nareit is the worldwide representative voice for REITs and …”.

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

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

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

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

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

Your homepage downloads 2.7 MB in 149 requests on a phone: scripts 1.3 MB (37), images 878 KiB (29) and HTML 297 KiB (38). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 2026 REITworld_980x551.jpg.webp at 980 px wide, shown at 310 px. Resized copies would save about 8 KiB.

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

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

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

3 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: 8 elements on the page fail this check, rated moderate by axe-core.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 16 characters: “Client Challenge”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

There is no robots.txt at reit.com/robots.txt, the first file search crawlers ask for.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

A phone browser shows 668 words, but the HTML your server sends has only 35. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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 668 words of visible text.

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

Opening the homepage sets 13 cookies, 1 of them by other companies (measured from a US location before any click).

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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.