Website review, no card needed

360homephoto.com logo

360homephoto.com website review

Visit site (opens in a new tab)Reviewed 22 November 202637 issues · 79 checks

This review found 37 issues worth fixing on 360homephoto.com, 12 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.2 sMay 30Nov 141.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.6 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.9 s
Oct 31, 20261.4 s
Nov 14, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
124 ms79 msMay 30Aug 192 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202684 ms
Jun 6, 202688 ms
Jun 13, 202691 ms
Jun 20, 2026105 ms
Jul 4, 2026119 ms
Jul 25, 202694 ms
Aug 1, 202692 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of 360homephoto.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 360homephoto.com at 0.6 s0.6 s
  2. 360homephoto.com at 1.2 s1.2 s
  3. 360homephoto.com at 1.7 s1.7 s
  4. 360homephoto.com at 2.3 s2.3 s
  5. 360homephoto.com at 2.9 s2.9 s
  6. 360homephoto.com at 3.5 s3.5 s
  7. 360homephoto.com at 4.1 s4.1 s
  8. 360homephoto.com at 4.7 s4.7 s

Speed

6 to fix64
  • Reduce unused JavaScript

    2.4 s · 421 KiB

    About 421 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Improve image delivery

    1.1 s · 1.2 MB

    16 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Use efficient cache lifetimes

    1.7 s · 231 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (231 KiB).

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    550 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

  • Minify JavaScript

    450 ms · 69 KiB

    69 KiB could be saved by minifying JavaScript.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, ZenDesk and jQuery CDN and others), adding 718 KiB and 327 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 18 KiB

    About 18 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    6 KiB

    Polyfills for old browsers add 6 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.

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 468 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 11.7 s

    11.7 s

    Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DEMO TOUR ORDER NOW”.

  • Time to Interactive: 11.7 s

    11.7 s

    The page becomes fully interactive after 11.7 s. Good is under 3.8 s.

  • Speed Index: 6.8 s

    6.8 s

    Visually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 2.8 s

    2.8 s

    The first text or image appears after 2.8 s on a phone. Good is under 1.8 s.

  • 6 images without width and height

    6 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 84 ms to 92 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 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.

3 checks passed
  • Largest content (LCP) got 23% faster for real visitors

    -23%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 72 ms

    72 ms

    Scripts block the page for only 72 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix58
  • Page weight: 3.5 MB in 69 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 69 requests on a phone: images 2.6 MB (28), scripts 752 KiB (21) and fonts 98 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (529 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.

  • 3 images below the first screen load straight away

    3 images further down the page (489 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    57 KiB

    1 image is downloaded at several times the size a phone draws it, for example vtbutton-orange.png at 511 px wide, shown at 56 px. Resized copies would save about 57 KiB.

  • About 1.0 g of CO₂ per visit

    0.99 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 118.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

9 to fixGoogle 6984
  • 29 text elements with low contrast

    29 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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.

  • 12 images without alt text

    12 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (12 elements)

    All page content should be contained by landmarks: 12 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.

  • 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.

  • 9 links without text

    9 visible links have no text or label, so screen readers cannot say where they go.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9279
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Canonical points to another host

    Your canonical URL points to 360photo.com, not 360homephoto.com, 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.

  • 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 X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 46 internal links, 5 external

    The homepage links to 46 pages on 360homephoto.com and 5 external pages.

4 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Real estate photography, 3D virtual tours, floor plans & drone services for realtors, builders & developers. Servicing …”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Real Estate Photography, Virtual Tours & Floor Plans Services”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.360homephoto.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://www.360homephoto.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 (527 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    https://www.360homephoto.com/a/slideshow and https://www.360homephoto.com/Slideshow all use the title “360 Home Photo Graphy - 49 Fenton Way”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.360homephoto.com/a/slideshow, https://www.360homephoto.com/Slideshow, https://www.360homephoto.com/highend, https://www.360homephoto.com/empty, https://www.360homephoto.com/condo and https://www.360homephoto.com/townhouse have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://www.360homephoto.com/photos, https://www.360homephoto.com/virtual-tuours, https://www.360homephoto.com/feature-sheets-, https://www.360homephoto.com/virtual-staging, https://www.360homephoto.com/drone and https://www.360homephoto.com/3d-floor-plan and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.360homephoto.com/highend and https://www.360homephoto.com/empty 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 21 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

3 to fixGoogle 7385
  • 14 small tap targets

    14 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 457 words of copy

    The homepage carries about 457 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “DEMO TOUR” and “ORDER NOW”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Demo”, “Contact Us” and “Demo Tour”.

  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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 360homephoto.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
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Liquid Web

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on 360homephoto.com, including 11 speed issues, 4 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25