Website review, no card needed

apartmentlist.com logo

apartmentlist.com website review

Visit site (opens in a new tab)Reviewed 23 October 202629 issues · 78 checks

This review found 29 issues worth fixing on apartmentlist.com, 5 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. 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
3.6 s2.9 sMay 2Oct 173.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.3 s
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.3 s
May 30, 20263.2 s
Jun 6, 20263.3 s
Jun 13, 20263.3 s
Jun 20, 20263.4 s
Jun 27, 20263.5 s
Jul 4, 20263.5 s
Jul 18, 20263.3 s
Jul 25, 20263.2 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
292 ms240 msMay 2Oct 17275 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026258 ms
May 9, 2026252 ms
May 16, 2026246 ms
May 23, 2026246 ms
May 30, 2026249 ms
Jun 6, 2026250 ms
Jun 13, 2026253 ms
Jun 20, 2026255 ms
Jun 27, 2026258 ms
Jul 4, 2026263 ms
Jul 18, 2026269 ms
Jul 25, 2026269 ms
Aug 8, 2026276 ms
Aug 15, 2026280 ms
Aug 22, 2026286 ms
Aug 29, 2026285 ms
Sep 5, 2026282 ms
Sep 12, 2026279 ms
Sep 19, 2026274 ms
Sep 26, 2026272 ms
Oct 3, 2026272 ms
Oct 10, 2026273 ms
Oct 17, 2026275 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 apartmentlist.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apartmentlist.com at 0.4 s0.4 s
  2. apartmentlist.com at 0.8 s0.8 s
  3. apartmentlist.com at 1.1 s1.1 s
  4. apartmentlist.com at 1.5 s1.5 s
  5. apartmentlist.com at 1.9 s1.9 s
  6. apartmentlist.com at 2.3 s2.3 s
  7. apartmentlist.com at 2.6 s2.6 s
  8. apartmentlist.com at 3.0 s3.0 s

Speed

5 to fix63
  • Mobile performance score: 63

    63/100

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

  • Render-blocking requests

    900 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Reduce unused JavaScript

    150 ms · 418 KiB

    About 418 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 7 long tasks on the main thread

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

  • Main-thread work: 3.3 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and uxcam.com and others), adding 426 KiB and 128 ms of main-thread time.

  • Use efficient cache lifetimes

    133 KiB

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

  • Minify JavaScript

    53 KiB

    53 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    14 KiB

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

  • Improve image delivery

    11 KiB

    1 image could be 11 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 14.5 s

    14.5 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Colorful Banner”.

  • Total Blocking Time: 836 ms

    836 ms

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

  • Real-user TTFB: 943 ms

    943 ms

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

7 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 137 ms

    137 ms

    Real visitors wait 137 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.7 s

    1.7 s

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Speed Index: 1.6 s

    1.6 s

    Visually, the page fills in at 1.6 s (Speed Index), inside the 3.4 s “good” threshold.

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 127 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 127 requests on a phone: scripts 1.2 MB (45), other files 666 KiB (65) and images 219 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.65 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • 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 10099
  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

4 to fixGoogle 9287
  • No canonical URL

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

  • Structured data has 1 problem

    Structured data found (Organization, Service and WebSite) but with 1 problem, for example “Service: no offers (price) block”.

  • No social preview image

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

  • 2 links with vague text

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

  • No X (Twitter) card tag

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

  • 87 internal links, 24 external

    The homepage links to 87 pages on apartmentlist.com and 24 external pages.

5 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Apartment List is a free service that helps you find the perfect apartment. Click to view move-in specials, photos, flo…”.

  • One H1 headline

    Your main headline reads: “Great apartments. no doom scroll.Stop Doom Scrolling Apartments.”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Apartment List - More than 7 Million Apartments for Rent”.

  • 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.apartmentlist.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

5 to fix60
  • 4 pages without a title

    https://www.apartmentlist.com/co/denver, https://www.apartmentlist.com/nc/charlotte, https://www.apartmentlist.com/ga/atlanta and https://www.apartmentlist.com/tn/nashville have no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.apartmentlist.com/quiz is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages share 2 titles

    https://www.apartmentlist.com/ca/san-francisco, https://www.apartmentlist.com/wa/seattle, https://www.apartmentlist.com/ca/san-diego, https://www.apartmentlist.com/mn/minneapolis, https://www.apartmentlist.com/nm/albuquerque and https://www.apartmentlist.com/oh/columbus all use the title “Download on the App Store”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.apartmentlist.com/quiz, https://www.apartmentlist.com/co/denver, https://www.apartmentlist.com/nc/charlotte, https://www.apartmentlist.com/ga/atlanta and https://www.apartmentlist.com/tn/nashville have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.apartmentlist.com/quiz, https://www.apartmentlist.com/il/chicago, https://www.apartmentlist.com/co/denver, https://www.apartmentlist.com/nc/charlotte, https://www.apartmentlist.com/ga/atlanta and https://www.apartmentlist.com/tn/nashville have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.apartmentlist.com/il/chicago 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.

  • 15 internal pages checked

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

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

Best practices

2 to fixGoogle 9687
  • 11 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://www.apartmentlist.com' has bee…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix69
  • 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 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.

  • Thin social proof

    Social proof on the homepage: 16 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • 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 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 724 words of copy

    The homepage carries about 724 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start matching” and “Get started”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Get started”, “Download on the App Store” and “Start matching now”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 9 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js

Company

Founded
2011

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on apartmentlist.com, including 10 speed issues, 4 SEO issues and 5 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