millcreekplaces.com website review

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

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

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

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

About 60 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.

5 third-party services load with your homepage (Accessibe Accessibility Overlay, JSDelivr CDN and Google CDN and others), adding 341 KiB and 218 ms of main-thread time.

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

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

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

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

Polyfills for old browsers add 8 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.

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

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

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

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

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

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

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

Your homepage downloads 4.9 MB in 42 requests on a phone: images 4.0 MB (23), scripts 632 KiB (9) and fonts 193 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

6 elements use ARIA attributes their role does not allow, which confuses screen readers.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Your title is 68 characters, so Google will cut it off around 60: “Apartments for Rent and Build-to-Rent Homes | Mill Creek Residential”.

There are 2 <h1> headlines (“Mill Creek Residential” and “Welcome to Mill Creek We're glad you're here.”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 61 pages on millcreekplaces.com and 19 external pages.

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

https://millcreekplaces.com/mission-core-values and https://millcreekplaces.com/about-us all use the title “About Us | Apartment Rentals | Mill Creek Residential”. Search engines can't tell which page to show for a search, so each competes with the others.

https://millcreekplaces.com/2025-esg-report has no <h1> headline, so visitors and search engines get no clear main topic.

https://millcreekplaces.com/2026-outlook has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

11 of 22 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 “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

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

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

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

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

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