Website review, no card needed

amandacamenisch.com logo

amandacamenisch.com website review

Visit site (opens in a new tab)Reviewed 11 November 202635 issues · 69 checks

This review found 35 issues worth fixing on amandacamenisch.com, 10 of them high impact, across 69 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

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

How it loaded on a phone

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

Speed

4 to fix75
  • Use efficient cache lifetimes

    3.6 s · 4.3 MB

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

  • Mobile performance score: 75

    75/100

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

  • Render-blocking requests

    850 ms

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

  • Reduce unused JavaScript

    410 ms · 132 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 181 KiB and 120 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 116 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

  • Legacy JavaScript

    8 KiB

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

2 checks passed
  • Main-thread work: 0.4 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

2 to fix67
  • Largest Contentful Paint: 14.0 s

    14.0 s

    Your largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You Know How to Interpret the Appearance of the Sky but Not…”.

  • Time to Interactive: 15.0 s

    15.0 s

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

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

4 checks passed
  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Speed Index: 1.2 s

    1.2 s

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

  • Total Blocking Time: 33 ms

    33 ms

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

Images and page weight

3 to fix45
  • Page weight: 4.5 MB in 29 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 29 requests on a phone: images 4.1 MB (13), scripts 319 KiB (8) and fonts 10 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.9 MB together. On a phone connection a single image that size takes seconds.

  • 13 images in older formats

    13 images (4.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.

  • About 1.3 g of CO₂ per visit

    1.26 g

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

2 checks passed
  • 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

7 to fixGoogle 7180
  • 15 tap targets too small

    15 tap targets are too small or too close together to hit reliably with a finger.

  • 13 images without alt text

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

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

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 16 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 22 WCAG 2.2 A/AA and best-practice rules on the phone render: 16 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 7557
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (16 characters)

    Your title is only 16 characters: “Amanda Camenisch”. 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 social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://amandacamenisch.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at amandacamenisch.com/robots.txt, the first file search crawlers ask for.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 36 internal links, 3 external

    The homepage links to 36 pages on amandacamenisch.com and 3 external pages.

1 checks passed
  • Canonical URL set

    The canonical URL is http://amandacamenisch.com/.

AI search readiness

1 to fix69
  • 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://amandacamenisch.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.

Other pages

4 to fix73
  • 12 pages point its canonical at the homepage

    https://amandacamenisch.com/work/corpus-interire, https://amandacamenisch.com/work/cosmograms, https://amandacamenisch.com/work/first-all-in-then-all-out, https://amandacamenisch.com/work/inside-out, https://amandacamenisch.com/work/making-the-room-sing and https://amandacamenisch.com/work/metamorphosis-1 and 6 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 13 pages share a title

    /, https://amandacamenisch.com/work/corpus-interire, https://amandacamenisch.com/work/cosmograms, https://amandacamenisch.com/work/first-all-in-then-all-out, https://amandacamenisch.com/work/inside-out and https://amandacamenisch.com/work/making-the-room-sing and 7 others all use the title “Amanda Camenisch”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://amandacamenisch.com/work/corpus-interire, https://amandacamenisch.com/work/cosmograms, https://amandacamenisch.com/work/first-all-in-then-all-out, https://amandacamenisch.com/work/inside-out, https://amandacamenisch.com/work/making-the-room-sing and https://amandacamenisch.com/work/metamorphosis-1 and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://amandacamenisch.com/work/corpus-interire, https://amandacamenisch.com/work/cosmograms, https://amandacamenisch.com/work/first-all-in-then-all-out, https://amandacamenisch.com/work/inside-out, https://amandacamenisch.com/work/making-the-room-sing and https://amandacamenisch.com/work/metamorphosis-1 and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8885
  • 15 small tap targets

    15 of 16 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 “Unexpected token '<'”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 85 words

    The homepage has only about 85 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.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Why Don’t You Get a Proper Job”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Why Don’t You Get a Proper Job”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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.

  • 4 cookies set on arrival

    4

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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 amandacamenisch.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
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

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

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