Website review, no card needed

merklescience.com logo

merklescience.com website review

Visit site (opens in a new tab)Reviewed 20 October 202640 issues · 86 checks

This review found 40 issues worth fixing on merklescience.com, 12 of them high impact, across 86 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

Real-visitor load time (LCP)75th percentile, phones
2.6 s2.0 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.4 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20262.0 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.2 s
Aug 15, 20262.1 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.5 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.2 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
169 ms85 msMay 2Oct 17145 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026115 ms
May 9, 2026109 ms
May 16, 202695 ms
May 23, 202698 ms
May 30, 2026101 ms
Jun 6, 2026101 ms
Jun 13, 2026113 ms
Jun 20, 2026119 ms
Jun 27, 2026125 ms
Jul 4, 2026133 ms
Jul 11, 2026142 ms
Jul 18, 2026137 ms
Jul 25, 2026138 ms
Aug 1, 2026139 ms
Aug 8, 2026132 ms
Aug 15, 2026159 ms
Aug 22, 2026139 ms
Aug 29, 2026134 ms
Sep 5, 2026134 ms
Sep 12, 2026141 ms
Sep 19, 2026153 ms
Sep 26, 2026154 ms
Oct 3, 2026152 ms
Oct 10, 2026136 ms
Oct 17, 2026145 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 merklescience.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. merklescience.com at 0.8 s0.8 s
  2. merklescience.com at 1.5 s1.5 s
  3. merklescience.com at 2.3 s2.3 s
  4. merklescience.com at 3.1 s3.1 s
  5. merklescience.com at 3.8 s3.8 s
  6. merklescience.com at 4.6 s4.6 s
  7. merklescience.com at 5.3 s5.3 s
  8. merklescience.com at 6.1 s6.1 s

Speed

9 to fix41
  • Render-blocking requests

    3.0 s

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

  • website-files.com adds 1.2 s

    1.2 s

    website-files.com costs a phone 1.2 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 41

    41/100

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

  • Main-thread work: 6.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (website-files.com, Google CDN and Hubspot and others), adding 3.3 MB and 2.4 s of main-thread time.

  • Google CDN adds 720 ms

    720 ms

    Google CDN costs a phone 720 ms of main-thread work and 1.1 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.

  • Reduce unused JavaScript

    642 KiB

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

  • Use efficient cache lifetimes

    553 KiB

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

  • Hubspot adds 221 ms

    221 ms

    Hubspot costs a phone 221 ms of main-thread work and 496 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.

  • Reduce unused CSS

    260 ms · 61 KiB

    About 61 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 ms faster on a phone.

  • 15 long tasks on the main thread

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

  • Improve image delivery

    61 KiB

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

  • Legacy JavaScript

    18 KiB

    Polyfills for old browsers add 18 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.

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

    2 ms

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

Core Web Vitals

10 to fix100
  • 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.

  • Time to Interactive: 26.0 s

    26.0 s

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

  • Speed Index: 13.9 s

    13.9 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

    Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AI-Powered Blockchain Analytics & Predictive Risk Platform”.

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Total Blocking Time: 925 ms

    925 ms

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

  • Tap response (INP) got 25% slower for real visitors

    +25%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 900 ms

    900 ms

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

  • 3 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

3 checks passed
  • 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 CLS: 0.03

    0.03

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

  • Cumulative Layout Shift: 0.038

    0.038

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

Images and page weight

2 to fix75
  • Page weight: 4.0 MB in 160 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 160 requests on a phone: scripts 2.0 MB (37), fonts 1.2 MB (17) and other files 448 KiB (54). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    31 KiB

    1 image is downloaded at several times the size a phone draws it, for example 6a33cbd16aaa9fa0e9246cb6_Untitled (500 x 300 px).png at 500 px wide, shown at 100 px. Resized copies would save about 31 KiB.

  • 1 image in older formats

    1 image (49 KiB) is 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.1 g of CO₂ per visit

    1.13 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 9093
  • 2 text elements with low contrast

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

  • <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 (40 elements)

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No page language

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

    Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 55 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 10081
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “The Predictive Crypto Risk & Intelligence Platform | Merkle Science”.

  • No structured data

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

  • 6 H1 headlines

    There are 6 <h1> headlines (“AI-Powered Blockchain Analytics & Predictive Risk…”, “Leading Innovator In Onchain Analytics And Threat…” and “What Industry Leaders Say”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 44 internal links, 15 external

    The homepage links to 44 pages on merklescience.com and 15 external pages.

4 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Next generation crypto threat detection, risk management and compliance for businesses, banks and government agencies. …”.

  • Canonical URL set

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

AI search readiness

1 to fix88
  • 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://www.merklescience.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.

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.

  • Text is in the HTML

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

Other pages

4 to fix79
  • 2 linked pages hidden from search

    https://www.merklescience.com/resources and https://www.merklescience.com/resources12 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.merklescience.com/resources and https://www.merklescience.com/resources12 all use the title “Resources | Merkle Science”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.merklescience.com/training-certifications, https://www.merklescience.com/press-reports, https://www.merklescience.com/events, https://www.merklescience.com/glossary, https://www.merklescience.com/merkle-watch and https://www.merklescience.com/experts-corner have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.merklescience.com/resources and https://www.merklescience.com/resources12 use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 19 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.

  • Canonical URLs point to themselves

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: jQuery is not defined”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

3 to fix81
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 1,110 words of copy

    The homepage carries about 1,110 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BOOK A DEMO” and “SCHEDULE A DEMO”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact us”, “Book a Demo” and “Schedule a Demo”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • Direct contact links

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

Privacy and tracking

  • 2 trackers load before any consent

    2

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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (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 merklescience.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
Webflow
Analytics
Google Tag Manager

Hiring

Hiring
21 open roles
Teams
Marketing (8), Customer Success (3), Data Science & Analytics (3), Engineering (2)
Job board
lever

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on merklescience.com, including 19 speed issues, 4 SEO issues and 3 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