Website review, no card needed
360toursofyork.com website review
Visit site (opens in a new tab)Reviewed 13 November 202649 issues · 87 checks
This review found 49 issues worth fixing on 360toursofyork.com, 19 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
69DClosest 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.0 s
2.1 s
3.1 s
4.1 s
5.1 s
6.2 s
7.2 s
8.2 s
Speed
Improve image delivery
2.6 s · 16.0 MB24 images could be 16.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 8.0 MB74 files are served with short cache lifetimes, so returning visitors download them again (8.0 MB).
Render-blocking requests
2.2 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Google CDN adds 1.7 s
1.7 sGoogle CDN costs a phone 1.7 s of main-thread work and 2.6 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: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.5 s
A phone's processor spends 6.5 s on main-thread work while loading, 4.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Maps and others), adding 3.7 MB and 2.4 s of main-thread time.
Reduce unused JavaScript
600 ms · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
300 ms · 77 KiBAbout 77 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 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).
Other Google APIs/SDKs adds 311 ms
311 msOther Google APIs/SDKs costs a phone 311 ms of main-thread work and 133 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 Maps adds 202 ms
202 msGoogle Maps costs a phone 202 ms of main-thread work and 443 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.
2,265 HTML elements
The page has 2,265 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 178 ms
178 msGoogle Tag Manager costs a phone 178 ms of main-thread work and 309 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 223 ms. During a long task the page ignores taps.
Minify CSS
10 KiB10 KiB could be saved by minifying CSS.
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
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: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 32.9 s
32.9 sThe page becomes fully interactive after 32.9 s. Good is under 3.8 s.
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “img”.
Total Blocking Time: 937 ms
937 msScripts block taps and scrolling for 937 ms in total while the page loads. Good is under 200 ms.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
10 images without width and height
10 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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 23.8 MB in 121 requests
23.8 MBYour homepage downloads 23.8 MB in 121 requests on a phone: images 18.0 MB (39), scripts 3.3 MB (32) and fonts 1.0 MB (16). Under 2 MB keeps phones on slow connections fast.
11 images over 500 KB
11 images weigh 13.3 MB together. On a phone connection a single image that size takes seconds.
14 images far larger than shown
10.7 MB14 images are downloaded at several times the size a phone draws them, for example Ruxanda-3.jpg at 2,000 px wide, shown at 316 px. Resized copies would save about 10.7 MB.
21 images in older formats
21 images (15.1 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.
17 images below the first screen load straight away
17 images further down the page (14.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.8 g of CO₂ per visit
6.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.75 g of CO₂e: 810.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
14 buttons without a name
14 buttons have no accessible name, so screen readers announce just “button”.
Scrollable region must have keyboard access (5 elements)
Scrollable region must have keyboard access: 5 elements on the page fail this check, rated serious by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (35 elements)
All page content should be contained by landmarks: 35 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.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
35 form fields without a label
35 form fields have no label, so screen readers announce an empty box and autofill guesses.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 13 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
111 links crawlers can't follow
111 links have no real href, so search engines can't follow them.
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.
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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
147 internal links, 28 external
The homepage links to 147 pages on 360toursofyork.com and 28 external pages.
4 checks passed
One H1 headline
Your main headline reads: “ON-DEMAND, QUALIFIED, LOCAL PHOTOGRAPHERS, DRONE PILOTS, VIDEOGRAPHERS AND VIRTUAL TOUR PRODUCERS”.
Title: 60 characters
Your title is a healthy 60 characters: “Professional Real Estate Photography - Real Estate Exposures”.
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://realestateexposures.com/sitemap_index.xml.
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://realestateexposures.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
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 (1,616 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 128 found) and read each the way a search engine does.
1 checks passed
Linked pages load
4 pages of 15 loaded without an error (the rest turned automated requests away).
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
2 checks passed
Tap targets are thumb-sized
14 of 17 tappable elements near the top are at least 24 px.
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.
A 11-field form
Your longest form asks for 11 fields (11 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,298 words of copy
The homepage carries about 1,298 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us” and “Schedule”.
12 calls to action
The homepage has 12 calls to action, for example “Schedule”, “Pricing” and “Contact Us”.
Social proof on the page
Social proof on the homepage: 9 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 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 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.
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.
10 other companies contacted
Loading the homepage contacts 10 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 360toursofyork.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- 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 49 issues on 360toursofyork.com, including 20 speed issues, 6 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.