Website review, no card needed

takeironseriously.com logo

takeironseriously.com website review

Visit site (opens in a new tab)Reviewed 20 November 202634 issues · 78 checks

This review found 34 issues worth fixing on takeironseriously.com, 14 of them high impact, across 78 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

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

How it loaded on a phone

  1. takeironseriously.com at 0.8 s0.8 s
  2. takeironseriously.com at 1.6 s1.6 s
  3. takeironseriously.com at 2.4 s2.4 s
  4. takeironseriously.com at 3.2 s3.2 s
  5. takeironseriously.com at 4.0 s4.0 s
  6. takeironseriously.com at 4.8 s4.8 s
  7. takeironseriously.com at 5.7 s5.7 s
  8. takeironseriously.com at 6.5 s6.5 s

Speed

8 to fix52
  • Render-blocking requests

    4.9 s

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

  • Reduce unused CSS

    3.1 s · 577 KiB

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

  • Mobile performance score: 52

    52/100

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

  • Improve image delivery

    350 ms · 526 KiB

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

  • Reduce unused JavaScript

    450 ms · 293 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Hotjar, Google Tag Manager and Optanon and others), adding 583 KiB and 590 ms of main-thread time.

  • Legacy JavaScript

    500 ms · 133 KiB

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

  • Minify JavaScript

    450 ms · 79 KiB

    79 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    150 ms · 108 KiB

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

  • 8 long tasks on the main thread

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

  • Minify CSS

    150 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • Document request latency

    75 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    50 ms

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

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

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 40 ms

    40 ms

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

Core Web Vitals

6 to fix62
  • Largest Contentful Paint: 9.3 s

    9.3 s

    Your largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Do you have enough iron”. Most of its time is resource load delay (4.5 s).

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Speed Index: 10.9 s

    10.9 s

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

  • Time to Interactive: 12.3 s

    12.3 s

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

  • Total Blocking Time: 239 ms

    239 ms

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

  • 3 images without width and height

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

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

1 checks passed
  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

2 to fix81
  • Page weight: 2.5 MB in 97 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 97 requests on a phone: scripts 881 KiB (44), images 867 KiB (15) and stylesheets 625 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    hero-banner1.jpeg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 4 images in older formats

    4 images (422 KiB) 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 0.7 g of CO₂ per visit

    0.72 g

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

1 checks passed
  • 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 9697
  • 8 text elements with low contrast

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

  • 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 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

7 to fixGoogle 4663
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 4 links crawlers can't follow

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

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Invalid hreflang

    Your hreflang tags are invalid, so Google may show the wrong language version.

  • Open Graph partly set

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

  • No X (Twitter) card tag

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

  • 64 internal links, 10 external

    The homepage links to 64 pages on takeironseriously.com and 10 external pages.

4 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Iron deficiency occurs when your body’s demand outstrips your natural supply. Find out about treatment, how to manage i…”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Homepage | Take Iron Seriously”.

  • Canonical URL set

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

  • XML sitemap found

    Your XML sitemap is reachable at http://takeironseriously.com/sitemap.xml.

AI search readiness

2 to fix53
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • 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://takeironseriously.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

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

Other pages

4 to fix76
  • 11 pages point its canonical at the homepage

    https://takeironseriously.com/ar, https://takeironseriously.com/es, https://takeironseriously.com/el, https://takeironseriously.com/ja, https://takeironseriously.com/it and https://takeironseriously.com/pt and 5 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.

  • 12 pages share a title

    /, https://takeironseriously.com/ar, https://takeironseriously.com/es, https://takeironseriously.com/el, https://takeironseriously.com/ja and https://takeironseriously.com/it and 6 others all use the title “Homepage | Take Iron Seriously”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages share a meta description

    https://takeironseriously.com/ar, https://takeironseriously.com/es, https://takeironseriously.com/el, https://takeironseriously.com/ja, https://takeironseriously.com/it and https://takeironseriously.com/pt and 5 others use the same meta description. A description written for each page earns more clicks.

  • 11 pages without an H1

    https://takeironseriously.com/ar, https://takeironseriously.com/es, https://takeironseriously.com/el, https://takeironseriously.com/ja, https://takeironseriously.com/it and https://takeironseriously.com/pt and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages slow to respond

    https://takeironseriously.com/patient-stories, https://takeironseriously.com/talk-your-doctor, https://takeironseriously.com/resources, https://takeironseriously.com/raising-awareness, https://takeironseriously.com/ar and https://takeironseriously.com/es and 7 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://fast.fonts.net/t/1.css?apiType=css&projectid=094daca1-8fe2-4799-a077-34fe74218f4b' violates the …”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 673 words of copy

    The homepage carries about 673 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Talk to Your Doctor” and “Talk To Your Doctor”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

  • Direct contact links

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

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Tag Manager, Hotjar and Microsoft Clarity (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 1 of them by other companies (measured from a US location before any click).

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with 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 takeironseriously.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
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on takeironseriously.com, including 14 speed issues, 7 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