Website review, no card needed
520tucson.com website review
Visit site (opens in a new tab)Reviewed 7 November 202658 issues · 94 checks
This review found 58 issues worth fixing on 520tucson.com, 26 of them high impact, across 94 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
60DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.3 s
2.5 s
3.8 s
5.0 s
6.3 s
7.5 s
8.8 s
10.1 s
Speed
Use efficient cache lifetimes
21.6 s · 9.9 MB34 files are served with short cache lifetimes, so returning visitors download them again (9.9 MB).
Improve image delivery
10.4 s · 6.1 MB13 images could be 6.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.4 s faster on a phone.
Reduce unused JavaScript
13.8 s · 2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 13.8 s faster on a phone.
Render-blocking requests
11.3 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 11.3 s.
Document request latency
2.3 s · 52 KiBThe HTML itself could arrive about 2.3 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
2.3 sReduce initial server response time. Google estimates savings of 2.3 s on a phone.
Reduce unused CSS
1.8 s · 275 KiBAbout 275 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Google CDN adds 1.3 s
1.3 sGoogle CDN costs a phone 1.3 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Server response: 2.4 s
2.4 sYour server takes 2.4 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Google Maps and others), adding 6.1 MB and 2.2 s of main-thread time.
Legacy JavaScript
750 ms · 89 KiBPolyfills for old browsers add 89 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 750 ms faster on a phone.
Google Tag Manager adds 409 ms
409 msGoogle Tag Manager costs a phone 409 ms of main-thread work and 375 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.
bullseyeplus.com adds 0 ms
0 msbullseyeplus.com costs a phone 0 ms of main-thread work and 3.7 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 362 ms. During a long task the page ignores taps.
Google Maps adds 304 ms
304 msGoogle Maps costs a phone 304 ms of main-thread work and 406 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.
bullseye-platform.com adds 0 ms
0 msbullseye-platform.com costs a phone 0 ms of main-thread work and 317 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 JavaScript
160 ms · 27 KiB27 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 20 KiB20 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Core Web Vitals
First Contentful Paint: 11.5 s
11.5 sThe first text or image appears after 11.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 56.7 s
56.7 sYour largest element takes 56.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 25.5 s
25.5 sVisually, the page fills in at 25.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 58.0 s
58.0 sThe page becomes fully interactive after 58.0 s. Good is under 3.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
14 images without width and height
14 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.039
0.039The layout barely moves while loading (CLS 0.039, good is under 0.1).
Images and page weight
Page weight: 14.2 MB in 103 requests
14.2 MBYour homepage downloads 14.2 MB in 103 requests on a phone: images 9.4 MB (33), scripts 3.4 MB (35) and other files 768 KiB (9). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 4.9 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
3.3 MB6 images are downloaded at several times the size a phone draws them, for example 20260901171248132151000000-o.jpg at 3,000 px wide, shown at 306 px. Resized copies would save about 3.3 MB.
15 images in older formats
15 images (7.0 MB) 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.
6 images below the first screen load straight away
6 images further down the page (3.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.0 g of CO₂ per visit
4.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.03 g of CO₂e: 484.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (86 elements)
All page content should be contained by landmarks: 86 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.
27 form fields without a label
27 form fields have no label, so screen readers announce an empty box and autofill guesses.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 11 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (337 characters)
Your meta description is 337 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 https://luannprillaman.unitedrealestatespecialists.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at luannprillaman.unitedrealestatespecialists.com/robots.txt, the first file search crawlers ask for.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
59 internal links, 21 external
The homepage links to 59 pages on 520tucson.com and 21 external pages.
2 checks passed
One H1 headline
Your main headline reads: “THINKING OF SELLING YOUR HOUSE ?”.
Title: 35 characters
Your title is a healthy 35 characters: “Your Arizona REal Estate Specialist”.
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://luannprillaman.unitedrealestatespecialists.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.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,490 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://luannprillaman.unitedrealestatespecialists.com/community.htm and https://luannprillaman.unitedrealestatespecialists.com/newPage.htm all use the title “New Page”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://luannprillaman.unitedrealestatespecialists.com/community.htm, https://luannprillaman.unitedrealestatespecialists.com/newPage.htm, https://luannprillaman.unitedrealestatespecialists.com/findingagoodagent.htm, https://luannprillaman.unitedrealestatespecialists.com/preparingtobuyyourhome.htm, https://luannprillaman.unitedrealestatespecialists.com/findingaproperty.htm and https://luannprillaman.unitedrealestatespecialists.com/makinganoffer.htm and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://luannprillaman.unitedrealestatespecialists.com/community.htm, https://luannprillaman.unitedrealestatespecialists.com/orovalley.htm, https://luannprillaman.unitedrealestatespecialists.com/marana.htm, https://luannprillaman.unitedrealestatespecialists.com/catalina.htm, https://luannprillaman.unitedrealestatespecialists.com/vail.htm and https://luannprillaman.unitedrealestatespecialists.com/tucson.htm and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://luannprillaman.unitedrealestatespecialists.com/marana.htm, https://luannprillaman.unitedrealestatespecialists.com/vail.htm, https://luannprillaman.unitedrealestatespecialists.com/tucson.htm, https://luannprillaman.unitedrealestatespecialists.com/buyers.htm, https://luannprillaman.unitedrealestatespecialists.com/findingagoodagent.htm and https://luannprillaman.unitedrealestatespecialists.com/preparingtobuyyourhome.htm and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
4 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.
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
2 broken images
2 images failed to load on a phone, for example https://www.zillowstatic.com/static-mortgage/LIVE/calculator/affordability/images/piggy.svg.
5 small tap targets
5 of 19 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 “$.cookie is not a function”.
8 distorted images
8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
A 12-field form
Your longest form asks for 12 fields (0 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
About 1,367 words of copy
The homepage carries about 1,367 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BUY”.
5 calls to action
The homepage has 5 calls to action, for example “Preparing To Buy Your Home”, “Pricing Your Home” and “BUY”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 4 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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
2Opening 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.
16 other companies contacted
Loading the homepage contacts 16 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 520tucson.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
- Angular
- Analytics
- Google Analytics
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 58 issues on 520tucson.com, including 24 speed issues, 7 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.