Website review, no card needed
aaimi.net website review
Visit site (opens in a new tab)Reviewed 6 November 202625 issues · 63 checks
This review found 25 issues worth fixing on aaimi.net, 8 of them high impact, across 63 checks. The most urgent: 2 linked pages are broken. 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
73CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100. That is in Google's “good” band (90 and up).
Main-thread work: 0.0 s
A phone's processor spends 0.0 s on main-thread work while loading, 4 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
6 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 0.6 s
0.6 sThe first text or image appears after 0.6 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 0.6 s
0.6 sYour largest element renders in 0.6 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “body”.
Speed Index: 0.6 s
0.6 sVisually, the page fills in at 0.6 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 0.6 s
0.6 sThe page is fully interactive after 0.6 s.
Images and page weight
About 0.00 g of CO₂ per visit
0.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.00 g of CO₂e: 0.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1 KiB in 1 request
1 KiBYour homepage downloads 1 KiB in 1 request on a phone: HTML 1 KiB (1). That is a lean page.
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.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Error status code
The page answers with an error status, so search engines may drop it.
Title is long (144 characters)
Your title is 144 characters, so Google will cut it off around 60: “Real Estate Appraisal - home appraisal - appraiser - real estate appraiser - residential …”.
Canonical points to another host
Your canonical URL points to aaimi.appraiserxsites.com, not aaimi.net, so Google may credit that host instead.
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 (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
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 http://aaimi.net/sitemap.xml, so Google discovers your pages only by following links.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
41 internal links, 2 external
The homepage links to 41 pages on aaimi.net and 2 external pages.
1 checks passed
robots.txt in place
robots.txt is in place.
AI search readiness
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://aaimi.net/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (464 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages are broken
Your homepage links to https://aaimi.net/FaxanOrder and https://aaimi.net/ClientLogin, which answer with an error. Visitors hit a dead end and search engines drop them.
3 pages without a title
https://aaimi.net/orderanappraisal, https://aaimi.net/OrderanAppraisal and https://aaimi.net/DownloadAdobeAcrobat have no <title>, so Google invents the link text in results.
2 pages share a title
https://aaimi.net/contactus and https://aaimi.net/ContactUs all use the title “How to contact Us - Appraisal Associates, Inc. - Contact Us”. 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://aaimi.net/orderanappraisal, https://aaimi.net/OrderanAppraisal, https://aaimi.net/DownloadAdobeAcrobat, https://aaimi.net/RealEstateNews and https://aaimi.net/FAQ have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://aaimi.net/contactus and https://aaimi.net/ContactUs use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://aaimi.net/orderanappraisal, https://aaimi.net/feequote, https://aaimi.net/services, https://aaimi.net/contactus, https://aaimi.net/ContactUs and https://aaimi.net/OrderanAppraisal and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://aaimi.net/orderanappraisal and https://aaimi.net/OrderanAppraisal have 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 pages slow to respond
https://aaimi.net/orderanappraisal, https://aaimi.net/services, https://aaimi.net/contactus, https://aaimi.net/OrderanAppraisal, https://aaimi.net/EstateAppraisals and https://aaimi.net/DivorceAppraisals and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.
2 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
1 broken image
1 image failed to load on a phone, for example https://aaimi.net/.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://mktrsc.alamode.com/assets/js/tls/' violates the following Content Security Policy directive…”.
2 checks passed
Tap targets are thumb-sized
42 of 42 tappable elements near the top are at least 24 px.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 534 words of copy
The homepage carries about 534 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: “Order Online” and “Fee Quote”.
11 calls to action
The homepage has 11 calls to action, for example “Order Online”, “Fee Quote” and “Contact Us”.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
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.
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 aaimi.net, 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
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on aaimi.net, including 9 SEO issues and 2 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.