Website review, no card needed
uptownrents.com website review
Visit site (opens in a new tab)Reviewed 21 October 202638 issues · 83 checks
This review found 38 issues worth fixing on uptownrents.com, 12 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 875 ms |
| May 9, 2026 | 968 ms |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 94 ms |
| May 9, 2026 | 96 ms |
| May 16, 2026 | 96 ms |
| May 23, 2026 | 99 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 106 ms |
| Jun 13, 2026 | 111 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 108 ms |
| Jul 18, 2026 | 110 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 106 ms |
| Aug 15, 2026 | 109 ms |
| Aug 22, 2026 | 111 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 115 ms |
| Sep 12, 2026 | 120 ms |
| Sep 19, 2026 | 124 ms |
| Sep 26, 2026 | 119 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 89 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
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
Use efficient cache lifetimes
6.3 s · 1.2 MB14 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Render-blocking requests
5.2 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.2 s.
Improve image delivery
4.2 s · 883 KiB4 images could be 883 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.2 s faster on a phone.
Reduce unused JavaScript
2.7 s · 480 KiBAbout 480 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 63). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 132 KiBAbout 132 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, wordpressanalytics.com and Cloudflare CDN and others), adding 1.2 MB and 400 ms of main-thread time.
Google Tag Manager adds 374 ms
374 msGoogle Tag Manager costs a phone 374 ms of main-thread work and 797 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.
Cloudflare CDN adds 5 ms
5 msCloudflare CDN costs a phone 5 ms of main-thread work and 349 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.
Minify CSS
150 ms · 21 KiB21 KiB could be saved by minifying CSS.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 126 ms. During a long task the page ignores taps.
Document request latency
29 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 372 ms of it running JavaScript. That is comfortably low.
Server response: 23 ms
23 msYour server sent the HTML in 23 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 16.1 s
16.1 sYour largest element takes 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
First Contentful Paint: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Time to Interactive: 16.1 s
16.1 sThe page becomes fully interactive after 16.1 s. Good is under 3.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 42% slower for real visitors
+42%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 904 ms
904 msReal visitors wait 904 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 94 ms to 89 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 81 ms
81 msReal visitors wait 81 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 110 ms
110 msScripts block the page for only 110 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.5 MB in 48 requests
2.5 MBYour homepage downloads 2.5 MB in 48 requests on a phone: scripts 1.0 MB (18), images 997 KiB (9) and fonts 296 KiB (3). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
129 KiB2 images are downloaded at several times the size a phone draws them, for example GCNKAA_Logo.png at 250 px wide, shown at 31 px. Resized copies would save about 129 KiB.
2 images in older formats
2 images (143 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.
About 0.7 g of CO₂ per visit
0.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.70 g of CO₂e: 83.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Main landmark should not be contained in another landmark (1 element)
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 main landmark (1 element)
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)
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 3 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Uptown Rental Properties” and “Apartments in Cincinnati and NKY”). One clear main headline is easier for people and search engines.
Meta description is long (187 characters)
Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
21 internal links, 8 external
The homepage links to 21 pages on uptownrents.com and 8 external pages.
5 checks passed
Title: 59 characters
Your title is a healthy 59 characters: “Apartments For Rent Cincinnati Ohio | Uptown Rentals | Home”.
Canonical URL set
The canonical URL is https://uptownrents.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://uptownrents.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://uptownrents.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.
1 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.
Other pages
1 page without a meta description
https://uptownrents.com/vendors has no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://uptownrents.com/university-area, https://uptownrents.com/available-now, https://uptownrents.com/greater-cincinnati, https://uptownrents.com/uc, https://uptownrents.com/hyde-park and https://uptownrents.com/downtown-cincinnati and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was 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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
Thin social proof
Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 42 words
The homepage has only about 42 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
4 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Umami.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before 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.
3 cookies set on arrival
3Opening the homepage sets 3 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 uptownrents.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on uptownrents.com, including 16 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.