Website review, no card needed

frederikhermann.com logo

frederikhermann.com website review

Visit site (opens in a new tab)Reviewed 11 November 202631 issues · 73 checks

This review found 31 issues worth fixing on frederikhermann.com, 14 of them high impact, across 73 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 frederikhermann.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. frederikhermann.com at 0.5 s0.5 s
  2. frederikhermann.com at 1.0 s1.0 s
  3. frederikhermann.com at 1.5 s1.5 s
  4. frederikhermann.com at 2.0 s2.0 s
  5. frederikhermann.com at 2.5 s2.5 s
  6. frederikhermann.com at 3.0 s3.0 s
  7. frederikhermann.com at 3.5 s3.5 s
  8. frederikhermann.com at 4.0 s4.0 s

Speed

9 to fix55
  • Use efficient cache lifetimes

    9.4 s · 12.5 MB

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

  • Render-blocking requests

    5.5 s

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

  • Reduce unused JavaScript

    3.0 s · 626 KiB

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

  • Reduce unused CSS

    2.6 s · 667 KiB

    About 667 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.6 s faster on a phone.

  • Improve image delivery

    1.2 s · 883 KiB

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

  • Mobile performance score: 55

    55/100

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

  • Font display

    550 ms

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

  • Minify JavaScript

    450 ms · 93 KiB

    93 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 324 ms

    324 ms

    Google Tag Manager costs a phone 324 ms of main-thread work and 491 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, Google Analytics and Quantcast and others), adding 590 KiB and 364 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 32 KiB

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

  • 5 long tasks on the main thread

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

  • Minify CSS

    62 KiB

    62 KiB could be saved by minifying CSS.

  • 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, 515 ms of it running JavaScript. That is comfortably low.

  • Server response: 11 ms

    11 ms

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

Core Web Vitals

4 to fix65
  • Largest Contentful Paint: 18.1 s

    18.1 s

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

  • First Contentful Paint: 6.7 s

    6.7 s

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

  • Time to Interactive: 18.1 s

    18.1 s

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

  • Speed Index: 10.7 s

    10.7 s

    Visually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 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.

2 checks passed
  • Total Blocking Time: 129 ms

    129 ms

    Scripts block the page for only 129 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

3 to fix45
  • Page weight: 13.1 MB in 128 requests

    13.1 MB

    Your homepage downloads 13.1 MB in 128 requests on a phone: images 10.9 MB (39), scripts 1.4 MB (48) and stylesheets 711 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 6.5 MB together. On a phone connection a single image that size takes seconds.

  • 13 images in older formats

    13 images (7.3 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 3.7 g of CO₂ per visit

    3.72 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.72 g of CO₂e: 446.6 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

2 to fixGoogle 9197
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 20 links without text

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • No H1 headline

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

  • Meta description is long (161 characters)

    Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 3 links crawlers can't follow

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

  • 67 internal links, 5 external

    The homepage links to 67 pages on frederikhermann.com and 5 external pages.

6 checks passed
  • Title: 38 characters

    Your title is a healthy 38 characters: “Frederik Hermann | Marketing Executive”.

  • Canonical URL set

    The canonical URL is https://www.frederikhermann.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, Person and WebPage.

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

AI search readiness

100
  • Opted out of AI training for 1 crawler

    robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

4 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, logo, sameAs (social profiles) and description; url and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (265 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix78
  • 2 pages share a title

    https://frederikhermann.com/growth-hacking and https://frederikhermann.com/portfolio/growth-hacking-guide all use the title “The Beginner's Guide to Growth Hacking - Frederik Hermann”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://frederikhermann.com/portfolio-category/content, https://frederikhermann.com/portfolio-category/growth, https://frederikhermann.com/portfolio-category/interview, https://frederikhermann.com/portfolio-category/podcast and https://frederikhermann.com/portfolio-category/seo have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://frederikhermann.com/portfolio/growth-hacking-guide, whose canonical is https://frederikhermann.com/portfolio-item/growth-hacking-guide. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://frederikhermann.com/generative-engine-optimization, https://frederikhermann.com/deep-funnel-optimization, https://frederikhermann.com/growth-hacking, https://frederikhermann.com/viral-marketing, https://frederikhermann.com/blog and https://frederikhermann.com/portfolio-category/content and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://frederikhermann.com/portfolio-category/content, https://frederikhermann.com/portfolio-category/growth, https://frederikhermann.com/portfolio-category/interview, https://frederikhermann.com/portfolio-category/seo, https://frederikhermann.com/portfolio/how-small-businesses-can-grow-during-the-coronavirus-pandemic and https://frederikhermann.com/portfolio/aligning-marketing-and-sales-toward-a-common-goal 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 31 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.

  • 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
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.frederikhermann.com/wp-content/themes/ottar/framework/lib/icons-pack/elegant-icons/fonts…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 205 words

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

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, Quantcast and X (Twitter) 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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 2 of them by other companies (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 frederikhermann.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 | Google Tag Manager
Hosting
IONOS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on frederikhermann.com, including 13 speed issues, 3 SEO issues and 4 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