Website review, no card needed

magnetforensics.com logo

magnetforensics.com website review

Visit site (opens in a new tab)Reviewed 2 November 202635 issues · 90 checks

This review found 35 issues worth fixing on magnetforensics.com, 16 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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
5.6 s3.4 sMay 16Oct 313.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.3 s
May 23, 20265.1 s
May 30, 20265.1 s
Jun 6, 20265.2 s
Jun 13, 20265.3 s
Jun 20, 20265.3 s
Jun 27, 20265.1 s
Jul 4, 20264.7 s
Jul 11, 20264.3 s
Jul 18, 20264.1 s
Jul 25, 20264.1 s
Aug 1, 20264.2 s
Aug 8, 20264.3 s
Aug 15, 20264.3 s
Aug 22, 20264.4 s
Aug 29, 20264.3 s
Sep 5, 20264.4 s
Sep 12, 20263.9 s
Sep 19, 20263.8 s
Sep 26, 20263.8 s
Oct 3, 20263.7 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Oct 24, 20263.7 s
Oct 31, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
274 ms185 msMay 16Oct 31253 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026235 ms
May 23, 2026242 ms
May 30, 2026249 ms
Jun 6, 2026255 ms
Jun 13, 2026255 ms
Jun 20, 2026264 ms
Jun 27, 2026261 ms
Jul 4, 2026261 ms
Jul 11, 2026260 ms
Jul 18, 2026260 ms
Jul 25, 2026260 ms
Aug 1, 2026259 ms
Aug 8, 2026257 ms
Aug 15, 2026242 ms
Aug 22, 2026241 ms
Aug 29, 2026232 ms
Sep 5, 2026234 ms
Sep 12, 2026200 ms
Sep 19, 2026195 ms
Sep 26, 2026201 ms
Oct 3, 2026203 ms
Oct 10, 2026225 ms
Oct 17, 2026248 ms
Oct 24, 2026253 ms
Oct 31, 2026253 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 magnetforensics.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. magnetforensics.com at 1.4 s1.4 s
  2. magnetforensics.com at 2.8 s2.8 s
  3. magnetforensics.com at 4.2 s4.2 s
  4. magnetforensics.com at 5.7 s5.7 s
  5. magnetforensics.com at 7.1 s7.1 s
  6. magnetforensics.com at 8.5 s8.5 s
  7. magnetforensics.com at 9.9 s9.9 s
  8. magnetforensics.com at 11.3 s11.3 s

Speed

13 to fix31
  • Reduce unused JavaScript

    4.7 s · 3.9 MB

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

  • Render-blocking requests

    1.6 s

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

  • Reduce unused CSS

    1.2 s · 273 KiB

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

  • Main-thread work: 14.2 s

    A phone's processor spends 14.2 s on main-thread work while loading, 7.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 31

    31/100

    Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 3,196 HTML elements

    The page has 3,196 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Vimeo, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 7.0 MB and 1.8 s of main-thread time.

  • Vimeo adds 897 ms

    897 ms

    Vimeo costs a phone 897 ms of main-thread work and 5.7 MB 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.

  • Use efficient cache lifetimes

    500 ms · 673 KiB

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

  • Google Tag Manager adds 570 ms

    570 ms

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

    532 KiB

    19 images could be 532 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    300 ms · 86 KiB

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    160 ms · 53 KiB

    53 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

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

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

    24 ms

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

Core Web Vitals

10 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: 19.5 s

    19.5 s

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

  • Speed Index: 25.7 s

    25.7 s

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

  • Time to Interactive: 58.4 s

    58.4 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 13 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

4 checks passed
  • Real-user INP: 156 ms

    156 ms

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

  • Real-user CLS: 0.01

    0.01

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

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

    -29%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.3 s to 3.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

3 to fix53
  • Page weight: 10.3 MB in 249 requests

    10.3 MB

    Your homepage downloads 10.3 MB in 249 requests on a phone: scripts 6.7 MB (69), images 2.1 MB (64) and stylesheets 562 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • 11 images in older formats

    11 images (1.4 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.

  • 11 images below the first screen load straight away

    11 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.9 g of CO₂ per visit

    2.91 g

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

3 to fixGoogle 9596
  • 4 tap targets too small

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

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

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 40 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (BreadcrumbList, ImageObject, LocalBusiness and Organization) but with 1 problem, for example “SiteNavigationElement: url is not an absolute URL ("https://www.magnetforensics.com/products/magnet-griffeye")”.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 231 internal links, 30 external

    The homepage links to 231 pages on magnetforensics.com and 30 external pages.

7 checks passed
  • Meta description: 122 characters

    Your meta description is 122 characters: “Gain an Investigative Edge. We provide organizations with innovative tools to investigate cyberattacks and digital crim…”.

  • One H1 headline

    Your main headline reads: “Your Investigative Edge”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Magnet Forensics | Gain an Investigative Edge”.

  • Canonical URL set

    The canonical URL is https://www.magnetforensics.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://www.magnetforensics.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.magnetforensics.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.

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

3 to fixGoogle 5880
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.net/action/0?ti=136011466&tm=gtm002&Ver=2&mid=6ffca5f1-fc68-4815-8aac-5e42b154e8b9&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Magnet%20Forensics%20%7C%20Gain%20an%20Inves.

  • 2 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix89
  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 968 words of visible text.

8 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “GET STARTED TODAY”, “get started for free” and “Contact us”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 87 testimonial or review blocks, 11 customer or partner logos and “over 6,000 customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 5 trackers load before any consent

    5

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

  • 17 cookies set on arrival

    17

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

  • 44 other companies contacted

    Loading the homepage contacts 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 magnetforensics.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 Tag Manager
Hosting
Fastly

Hiring

Hiring
40 open roles
Teams
Engineering (10), Sales (9), Finance (4), Customer Success (3)
Job board
lever

Company

Employees
274

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 magnetforensics.com, including 23 speed issues, 2 SEO issues and 1 conversion gap. 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