Website review, no card needed

aerialperspectiveoc.com logo

aerialperspectiveoc.com website review

Visit site (opens in a new tab)Reviewed 17 November 202633 issues · 81 checks

This review found 33 issues worth fixing on aerialperspectiveoc.com, 9 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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
4.5 s3.2 sMay 30Nov 143.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.2 s
Jun 6, 20264.2 s
Jun 13, 20264.1 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20264.2 s
Jul 11, 20264.2 s
Jul 18, 20264.2 s
Jul 25, 20264.2 s
Aug 1, 20264.2 s
Aug 8, 20264.2 s
Aug 15, 20264.3 s
Aug 22, 20264.3 s
Aug 29, 20264.4 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.3 s
Sep 26, 20264.3 s
Oct 3, 20264.2 s
Oct 10, 20264.0 s
Oct 17, 20263.7 s
Oct 24, 20263.5 s
Oct 31, 20263.4 s
Nov 7, 20263.4 s
Nov 14, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
247 ms193 msMay 30Nov 14199 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026241 ms
Jun 6, 2026240 ms
Jun 13, 2026239 ms
Jun 20, 2026239 ms
Jun 27, 2026240 ms
Jul 4, 2026240 ms
Jul 11, 2026241 ms
Jul 18, 2026241 ms
Jul 25, 2026239 ms
Aug 1, 2026239 ms
Aug 8, 2026239 ms
Aug 15, 2026239 ms
Aug 22, 2026239 ms
Aug 29, 2026239 ms
Sep 5, 2026239 ms
Sep 12, 2026240 ms
Sep 19, 2026240 ms
Sep 26, 2026239 ms
Oct 3, 2026234 ms
Oct 10, 2026228 ms
Oct 17, 2026222 ms
Oct 24, 2026213 ms
Oct 31, 2026208 ms
Nov 7, 2026204 ms
Nov 14, 2026199 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 aerialperspectiveoc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aerialperspectiveoc.com at 0.4 s0.4 s
  2. aerialperspectiveoc.com at 0.8 s0.8 s
  3. aerialperspectiveoc.com at 1.1 s1.1 s
  4. aerialperspectiveoc.com at 1.5 s1.5 s
  5. aerialperspectiveoc.com at 1.9 s1.9 s
  6. aerialperspectiveoc.com at 2.3 s2.3 s
  7. aerialperspectiveoc.com at 2.6 s2.6 s
  8. aerialperspectiveoc.com at 3.0 s3.0 s

Speed

3 to fix92
  • Render-blocking requests

    1.4 s

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Reduce unused CSS

    300 ms · 71 KiB

    About 71 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.

  • Google Tag Manager adds 268 ms

    268 ms

    Google Tag Manager costs a phone 268 ms of main-thread work and 339 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Parse.ly and others), adding 608 KiB and 483 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 232 KiB

    About 232 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    186 KiB

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

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    24 KiB

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

3 checks passed
  • Mobile performance score: 92

    92/100

    Your mobile performance score is 92. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.9 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

5 to fix100
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Time to Interactive: 8.3 s

    8.3 s

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

  • Real-user FCP: 2.3 s

    2.3 s

    Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.5 s

    1.5 s

    Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 2.3 s

    2.3 s

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

9 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

    Real visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 103 ms

    103 ms

    Real visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 16% faster for real visitors

    -16%

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

  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

  • Total Blocking Time: 194 ms

    194 ms

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

  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “aerialperspectiveoc.wordpress.com doesn't exist”.

  • Speed Index: 2.6 s

    2.6 s

    Visually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.23 g

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

4 checks passed
  • Page weight: 813 KiB in 43 requests

    813 KiB

    Your homepage downloads 813 KiB in 43 requests on a phone: scripts 684 KiB (19), stylesheets 92 KiB (8) and HTML 30 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

8 to fixGoogle 8688
  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 33 links without text

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

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

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 33 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: 33 passed and 7 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 6660
  • No H1 headline

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (13 characters)

    Your title is only 13 characters: “WordPress.com”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

  • No X (Twitter) card tag

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

  • 88 internal links, 28 external

    The homepage links to 88 pages on aerialperspectiveoc.com and 28 external pages.

3 checks passed
  • Meta description: 72 characters

    Your meta description is 72 characters: “WordPress.com is the best place for your personal blog or business site.”.

  • 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://wordpress.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

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.

  • llms.txt published

    The site publishes https://wordpress.com/llms.txt (10 KiB, 54 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix75
  • 1 linked page hidden from search

    https://wordpress.com/setup/domain-transfer is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages share a title

    https://wordpress.com/typo?subdomain=aerialperspectiveoc, https://wordpress.com/start and https://wordpress.com/setup/domain-transfer all use the title “WordPress.com”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://wordpress.com/setup/domain-transfer has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://wordpress.com/support and https://wordpress.com/setup/domain-transfer have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://wordpress.com/start has 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 36 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=4074038&Ver=2&mid=95b4e185-14e5-4513-80b7-a788ae06beb6&bo=1&sid=e1154720e2b511f19f0e4d1fc0e235c2&vid=e11579a0e2b511f1bb2c9b40551cccc4&vids=1&msclkid=N&pi=918639831&lg=.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    47 of 50 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 57 words

    The homepage has only about 57 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Pricing”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Pricing”, “Get started” and “Contact”.

  • Analytics in place

    Analytics detected: Meta Pixel.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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.

  • 17 other companies contacted

    Loading the homepage contacts 17 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 aerialperspectiveoc.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
WordPress.com

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on aerialperspectiveoc.com, including 8 speed issues, 6 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

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