Website review, no card needed
357property.com website review
Visit site (opens in a new tab)Reviewed 14 November 202641 issues · 83 checks
This review found 41 issues worth fixing on 357property.com, 16 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
56FClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.1 s
1.7 s
2.2 s
2.8 s
3.3 s
3.9 s
4.4 s
Speed
Use efficient cache lifetimes
16.4 s · 3.4 MB38 files are served with short cache lifetimes, so returning visitors download them again (3.4 MB).
Render-blocking requests
15.6 s26 files block the first paint until they finish downloading. Deferring or inlining them could save about 15.6 s.
Reduce unused JavaScript
5.7 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.
Reduce unused CSS
5.5 s · 870 KiBAbout 870 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.5 s faster on a phone.
Minify CSS
1.1 s · 83 KiB83 KiB could be saved by minifying CSS.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
600 ms · 204 KiB8 images could be 204 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Legacy JavaScript
400 ms · 62 KiBPolyfills for old browsers add 62 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Minify JavaScript
150 ms · 35 KiB35 KiB could be saved by minifying JavaScript.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 61 ms. During a long task the page ignores taps.
Document request latency
27 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
2 third-party services on the page
2 third-party services load with your homepage (GitHub and Google Fonts), adding 88 KiB and 3 ms of main-thread time.
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: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 284 ms of it running JavaScript. That is comfortably low.
Server response: 181 ms
181 msYour server sent the HTML in 181 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 16.0 s
16.0 sThe first text or image appears after 16.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 19.4 s
19.4 sYour 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 “1 BED FIRST FLOOR FLAT, FULLY FURNISHED, WITH A COMMUNAL PO…”.
Speed Index: 16.0 s
16.0 sVisually, the page fills in at 16.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 20.8 s
20.8 sThe page becomes fully interactive after 20.8 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.5
0.5The layout shifts by 0.5 while loading, so content jumps under the reader's thumb. Good is under 0.1.
7 images without width and height
7 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
Total Blocking Time: 3 ms
3 msScripts block the page for only 3 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.5 MB in 45 requests
3.5 MBYour homepage downloads 3.5 MB in 45 requests on a phone: scripts 1.6 MB (18), stylesheets 904 KiB (9) and images 792 KiB (12). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (512 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 below the first screen load straight away
2 images further down the page (70 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 120.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
21 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 25 WCAG 2.2 A/AA and best-practice rules on the phone render: 21 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (17 characters)
Your title is only 17 characters: “357PROPERTY - 357”. Between 30 and 65 characters leaves room to say what you do and for whom.
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 short (14 characters)
Your meta description is only 14 characters: “Property sales”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
No XML sitemap
No XML sitemap at https://357property.com/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
46 internal links, 3 external
The homepage links to 46 pages on 357property.com and 3 external pages.
1 checks passed
One H1 headline
Your main headline reads: “Great places to visit”.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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://357property.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (425 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://357property.com/properties/properties-latest and https://357property.com/properties/latest-3 have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://357property.com/companies, https://357property.com/companies/agents, https://357property.com/contact-us and https://357property.com/smart-search use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://357property.com/properties/properties-latest, https://357property.com/properties/latest-3, https://357property.com/companies, https://357property.com/companies/agents and https://357property.com/smart-search have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://357property.com/companies/agents 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.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 9 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 9 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
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
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.
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.
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 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.
About 330 words of copy
The homepage carries about 330 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “[object Object]”.
9 calls to action
The homepage has 9 calls to action, for example “Contact Us”, “Buy Now” and “Buy Extension”.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 357property.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- InMotion Hosting, Inc.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on 357property.com, including 15 speed issues, 8 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.