Website review, no card needed
4amyteam.com website review
Visit site (opens in a new tab)Reviewed 17 November 202628 issues · 75 checks
This review found 28 issues worth fixing on 4amyteam.com, 9 of them high impact, across 75 checks. The most urgent: reduce unused JavaScript. 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
74CClosest 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
3.8 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.
Render-blocking requests
1.6 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Reduce unused CSS
1.1 s · 202 KiBAbout 202 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, myrealestateplatform.com and Other Google APIs/SDKs and others), adding 3.7 MB and 1.2 s of main-thread time.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 619 ms
619 msGoogle Tag Manager costs a phone 619 ms of main-thread work and 958 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.
myrealestateplatform.com adds 453 ms
453 msmyrealestateplatform.com costs a phone 453 ms of main-thread work and 2.3 MB 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 392 ms. During a long task the page ignores taps.
2,198 HTML elements
The page has 2,198 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 834 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
150 ms · 22 KiB1 image could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
20 KiB4 files are served with short cache lifetimes, so returning visitors download them again (20 KiB).
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.5 s
16.5 sYour largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 24.7 s
24.7 sThe page becomes fully interactive after 24.7 s. Good is under 3.8 s.
Total Blocking Time: 737 ms
737 msScripts block taps and scrolling for 737 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.106
0.106The layout shifts by 0.106 while loading, so content jumps under the reader's thumb. Good is under 0.1.
3 images without width and height
3 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
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.8 MB in 58 requests
3.8 MBYour homepage downloads 3.8 MB in 58 requests on a phone: scripts 2.1 MB (18), fonts 1.4 MB (8) and stylesheets 220 KiB (6). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (65 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 1.1 g of CO₂ per visit
1.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 130.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
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.
All page content should be contained by landmarks (93 elements)
All page content should be contained by landmarks: 93 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.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
40 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: 40 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
131 internal links, 15 external
The homepage links to 131 pages on 4amyteam.com and 15 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Realtor Amy McDougald Eckard and The Amy Team with Keller Williams Chervenic Realty provide home buyers and sellers wit…”.
One H1 headline
Your main headline reads: “Your Local Real Estate Agents”.
Title: 62 characters
Your title is a healthy 62 characters: “Real Estate Agent Amy McDougald Eckard | Realtor in Aurora, OH”.
Canonical URL set
The canonical URL is https://www.4amyteam.com/.
Structured data in place
Structured data found: BreadcrumbList, LocalBusiness, Organization, Person and RealEstateAgent.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.4amyteam.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 4 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
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,306 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.4amyteam.com/llms.txt (4 KiB, 37 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static.myrealestateplatform.com/Valhalla/assets/dist/valhalla-vendor-styles.css?v=…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
36 of 36 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 949 words of copy
The homepage carries about 949 words of visible text.
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Ready To Buy Survey” and “Contact Us”.
23 calls to action
The homepage has 23 calls to action, for example “Ready To Buy Survey”, “Contact Us” and “Sign Up”.
5 short forms
5 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: a star rating and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 3 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.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
19 other companies contacted
Loading the homepage contacts 19 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 4amyteam.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
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on 4amyteam.com, including 16 speed issues and 1 SEO issue. 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.