Website review, no card needed

aftershoot.com logo

aftershoot.com website review

Visit site (opens in a new tab)Reviewed 31 October 202632 issues · 74 checks

This review found 32 issues worth fixing on aftershoot.com, 14 of them high impact, across 74 checks. The most urgent: use efficient cache lifetimes. 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
3.4 s2.5 sMay 9Oct 242.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.2 s
May 23, 20263.3 s
May 30, 20263.1 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.7 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.7 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
500 ms117 msMay 9Oct 24336 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026162 ms
May 16, 2026161 ms
May 23, 2026175 ms
May 30, 2026177 ms
Jun 6, 2026179 ms
Jun 13, 2026181 ms
Jun 20, 2026184 ms
Jun 27, 2026198 ms
Jul 4, 2026205 ms
Jul 11, 2026226 ms
Jul 18, 2026227 ms
Jul 25, 2026207 ms
Aug 1, 2026214 ms
Aug 8, 2026212 ms
Aug 15, 2026211 ms
Aug 22, 2026238 ms
Aug 29, 2026241 ms
Sep 5, 2026241 ms
Sep 12, 2026387 ms
Sep 19, 2026396 ms
Sep 26, 2026432 ms
Oct 3, 2026456 ms
Oct 10, 2026322 ms
Oct 17, 2026336 ms
Oct 24, 2026336 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 aftershoot.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aftershoot.com at 0.6 s0.6 s
  2. aftershoot.com at 1.3 s1.3 s
  3. aftershoot.com at 1.9 s1.9 s
  4. aftershoot.com at 2.6 s2.6 s
  5. aftershoot.com at 3.2 s3.2 s
  6. aftershoot.com at 3.8 s3.8 s
  7. aftershoot.com at 4.5 s4.5 s
  8. aftershoot.com at 5.1 s5.1 s

Speed

12 to fix32
  • Use efficient cache lifetimes

    9.8 s · 1.5 MB

    16 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

  • Reduce unused JavaScript

    7.2 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.2 s faster on a phone.

  • Improve image delivery

    1.1 s · 2.6 MB

    31 images could be 2.6 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.

  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32. 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, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Intercom and Google Tag Manager and others), adding 1.0 MB and 1.1 s of main-thread time.

  • Legacy JavaScript

    500 ms · 33 KiB

    Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.

  • 19 long tasks on the main thread

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

  • Facebook adds 411 ms

    411 ms

    Facebook costs a phone 411 ms of main-thread work and 282 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.

  • Intercom adds 320 ms

    320 ms

    Intercom costs a phone 320 ms of main-thread work and 232 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 Tag Manager adds 206 ms

    206 ms

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

  • Font display

    50 ms

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

  • Duplicated JavaScript

    7 KiB

    7 KiB JavaScript is shipped twice across bundles.

  • 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: 9 ms

    9 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 41.0 s

    41.0 s

    Your largest element takes 41.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 42.5 s

    42.5 s

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

  • Total Blocking Time: 2.8 s

    2.8 s

    Scripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 10.3 s

    10.3 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user INP: 260 ms

    260 ms

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

  • Tap response (INP) got 108% slower for real visitors

    +108%

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

  • 12 images without width and height

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

6 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 CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 742 ms

    742 ms

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

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

    -15%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix0
  • Page weight: 9.8 MB in 182 requests

    9.8 MB

    Your homepage downloads 9.8 MB in 182 requests on a phone: images 6.7 MB (81), scripts 2.5 MB (32) and fonts 430 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • About 2.8 g of CO₂ per visit

    2.77 g

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

Accessibility

3 to fix88
  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 9 text elements with low contrast

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

  • 6 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

SEO

2 to fixGoogle 9289
  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “Aftershoot | Best AI Culling, Editing & Retouching Software for Photographers”.

  • Structured data has 1 problem

    Structured data found (Article, FAQPage, ImageObject and Organization) but with 1 problem, for example “Article: missing datePublished”.

  • 46 internal links, 20 external

    The homepage links to 46 pages on aftershoot.com and 20 external pages.

6 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “AI photo editing software that culls, edits & retouches for you. Aftershoot helps photographers deliver faster — withou…”.

  • One H1 headline

    Your main headline reads: “You shoot. Aftershoot handles the rest.”.

  • Canonical URL set

    The canonical URL is https://aftershoot.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://aftershoot.com/sitemap_index.xml.

AI search readiness

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • llms.txt published

    The site publishes https://aftershoot.com/llms.txt (17 KiB, 67 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 2 pages without an H1

    https://aftershoot.com/tools and https://aftershoot.com/pricing have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://aftershoot.com/tools 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.

  • 1 page slow to respond

    https://aftershoot.com/tools took over 3 s to send its 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.

6 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 meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 9693
  • 1 console error

    1 error was logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 404 (Not Found)”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • 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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • 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,814 words of copy

    The homepage carries about 1,814 words of visible text.

5 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Pricing”, “Join Our Community” and “Get Started”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo, a star rating, 1 trust badge and “1.7K+ Reviews”.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel and PostHog.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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 aftershoot.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
Analytics
Google Analytics | Segment | PostHog
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on aftershoot.com, including 21 speed issues, 2 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