Website review, no card needed

fuckthepopulation.com logo

fuckthepopulation.com website review

Visit site (opens in a new tab)Reviewed 6 November 202631 issues · 78 checks

This review found 31 issues worth fixing on fuckthepopulation.com, 4 of them high impact, across 78 checks. The most urgent: <html> element must have a lang attribute (1 element). 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
1.2 s500 msMay 16Oct 31725 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026805 ms
May 23, 2026803 ms
May 30, 2026820 ms
Jun 6, 2026858 ms
Jun 13, 2026996 ms
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 2026625 ms
Jul 11, 2026595 ms
Jul 18, 2026587 ms
Jul 25, 2026583 ms
Aug 1, 2026626 ms
Aug 8, 2026751 ms
Aug 15, 2026820 ms
Aug 22, 2026839 ms
Aug 29, 2026739 ms
Sep 5, 2026746 ms
Sep 12, 2026795 ms
Sep 19, 2026803 ms
Sep 26, 2026899 ms
Oct 3, 2026953 ms
Oct 10, 2026748 ms
Oct 17, 2026745 ms
Oct 24, 2026717 ms
Oct 31, 2026725 ms
Real-visitor tap response (INP)75th percentile, phones
73 ms56 msMay 16Oct 3160 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202663 ms
May 23, 202663 ms
May 30, 202663 ms
Jun 6, 202664 ms
Jun 13, 202670 ms
Jun 20, 202670 ms
Jun 27, 202671 ms
Jul 4, 202661 ms
Jul 11, 202660 ms
Jul 18, 202659 ms
Jul 25, 202658 ms
Aug 1, 202660 ms
Aug 8, 202661 ms
Aug 15, 202662 ms
Aug 22, 202662 ms
Aug 29, 202661 ms
Sep 5, 202661 ms
Sep 12, 202661 ms
Sep 19, 202662 ms
Sep 26, 202662 ms
Oct 3, 202663 ms
Oct 10, 202660 ms
Oct 17, 202661 ms
Oct 24, 202660 ms
Oct 31, 202660 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 fuckthepopulation.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix94
  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google CDN and Shopify and others), adding 1.2 MB and 424 ms of main-thread time.

  • Reduce unused JavaScript

    523 KiB

    About 523 KiB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    500 ms

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

  • YouTube adds 373 ms

    373 ms

    YouTube costs a phone 373 ms of main-thread work and 1,005 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.

  • Improve image delivery

    300 ms · 80 KiB

    3 images could be 80 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    110 KiB

    About 110 KiB of CSS is downloaded but never applied on this page.

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    35 KiB

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

  • 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: 94

    94/100

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

  • Main-thread work: 1.4 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 11.4 s

    11.4 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

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

  • Speed Index: 3.4 s

    3.4 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 78 ms

    78 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 564 ms

    564 ms

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

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

    -10%

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

  • Total Blocking Time: 71 ms

    71 ms

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

2 to fix75
  • Page weight: 2.2 MB in 174 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 174 requests on a phone: scripts 1.1 MB (50), other files 805 KiB (108) and HTML 97 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    53 KiB

    1 image is downloaded at several times the size a phone draws it, for example ftp-records-icon.jpg at 1,000 px wide, shown at 45 px. Resized copies would save about 53 KiB.

  • About 0.6 g of CO₂ per visit

    0.61 g

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

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

Accessibility

4 to fixGoogle 8893
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

  • 2 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 3 images 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 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10079
  • Title is short (18 characters)

    Your title is only 18 characters: “FUCKTHEPOPULATION®”. 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.

  • Meta description is short (4 characters)

    Your meta description is only 4 characters: “FTP®”. 70 to 160 characters is enough to sell the click.

  • One H1 headline

    Your <h1> is empty.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 16 internal links, 5 external

    The homepage links to 16 pages on fuckthepopulation.com and 5 external pages.

3 checks passed
  • Canonical URL set

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

  • 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://fuckthepopulation.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://fuckthepopulation.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://fuckthepopulation.com/collections/shop, https://fuckthepopulation.com/pages/ftprecords and https://fuckthepopulation.com/pages/newsletter have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://fuckthepopulation.com/collections/shop, https://fuckthepopulation.com/pages/contact, https://fuckthepopulation.com/pages/terms-info and https://fuckthepopulation.com/pages/ftprecords have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://fuckthepopulation.com/collections/shop, https://fuckthepopulation.com/pages/contact, https://fuckthepopulation.com/pages/ftprecords and https://fuckthepopulation.com/pages/newsletter 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.

  • 5 internal pages checked

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

5 checks passed
  • Linked pages load

    All 5 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 5 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 7 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 8 words

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

1 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop” and “Contact”.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies, 1 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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 fuckthepopulation.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Minmaxify Order Limits · chimpstatic.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

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 fuckthepopulation.com, including 10 speed issues, 4 SEO issues and 5 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