Website review, no card needed

cozyprops.com logo

cozyprops.com website review

Visit site (opens in a new tab)Reviewed 20 November 202630 issues · 73 checks

This review found 30 issues worth fixing on cozyprops.com, 11 of them high impact, across 73 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of cozyprops.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix59
  • Use efficient cache lifetimes

    21.9 s · 5.9 MB

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

  • Reduce unused JavaScript

    3.1 s · 644 KiB

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

  • Improve image delivery

    2.2 s · 321 KiB

    2 images could be 321 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.2 s faster on a phone.

  • Render-blocking requests

    2.2 s

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

  • Reduce unused CSS

    770 ms · 324 KiB

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

  • Mobile performance score: 59

    59/100

    Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 216 ms

    216 ms

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

  • Google CDN adds 152 ms

    152 ms

    Google CDN costs a phone 152 ms of main-thread work and 382 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and jQuery CDN and others), adding 918 KiB and 459 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 395 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix61
  • Largest Contentful Paint: 72.8 s

    72.8 s

    Your largest element takes 72.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Banner 1”.

  • Time to Interactive: 74.6 s

    74.6 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Total Blocking Time: 250 ms

    250 ms

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

2 to fix60
  • Page weight: 15.1 MB in 47 requests

    15.1 MB

    Your homepage downloads 15.1 MB in 47 requests on a phone: images 13.6 MB (12), scripts 1.1 MB (15) and stylesheets 266 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    46 KiB

    1 image is downloaded at several times the size a phone draws it, for example logo.png at 1,653 px wide, shown at 184 px. Resized copies would save about 46 KiB.

  • 1 image in older formats

    1 image (52 KiB) is 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 4.3 g of CO₂ per visit

    4.28 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.28 g of CO₂e: 513.3 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 to fixGoogle 9798
  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • Title is long (115 characters)

    Your title is 115 characters, so Google will cut it off around 60: “Cambridge Property Management, Cambridge Property Managers, Cambridge Property Management…”.

  • No structured data

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

  • Meta description is long (184 characters)

    Your meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 15 internal links, 8 external

    The homepage links to 15 pages on cozyprops.com and 8 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Cozy Properties”.

  • Canonical URL set

    The canonical URL is https://www.cozyprops.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.cozyprops.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

  • No llms.txt

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

3 to fix75
  • 1 page without a title

    https://www.cozyprops.com/wc3-policy has no <title>, so Google invents the link text in results.

  • 3 pages without a meta description

    https://www.cozyprops.com/sitemap, https://www.cozyprops.com/privacy-policy and https://www.cozyprops.com/wc3-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.cozyprops.com/wc3-policy has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.cozyprops.com/cambridge-homes-for-rent 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.

  • 5 internal pages checked

    We fetched 5 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 5 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.

Best practices

1 to fixGoogle 10093
  • 9 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • No social proof

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

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

  • Only about 130 words

    The homepage has only about 130 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Maintenance Request” and “Contact Us”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Maintenance Request” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 cozyprops.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
jQuery
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on cozyprops.com, including 14 speed issues, 4 SEO issues and 3 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