shardeum.org website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Clarity and others), adding 492 KiB and 882 ms of main-thread time.

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

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

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

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

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

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

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

17 KiB could be saved by minifying CSS.

Desktop scores 90 but mobile only 48. A gap that wide usually means heavy scripts and images that hit phones hardest.

9 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Diagram: Shardeum tokenization layer connecting commodities…”.

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

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

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

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

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

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

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

Your homepage downloads 5.5 MB in 159 requests on a phone: images 4.3 MB (82), scripts 651 KiB (31) and stylesheets 264 KiB (30). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (270 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (67 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.

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

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

48 images have no alt text, which hurts accessibility and image search.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

The homepage links to 65 pages on shardeum.org and 118 external pages.

There is no https://shardeum.org/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.

https://shardeum.org/mica has no <title>, so Google invents the link text in results.

https://shardeum.org/campaigns, https://shardeum.org/shm-token-guide and https://shardeum.org/shardeum-node-resources are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://shardeum.org/mica and https://shardeum.org/events have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://shardeum.org/faq, whose canonical is https://shardeum.org/faq/general. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://shardeum.org/ecosystem, https://shardeum.org/mica, https://shardeum.org/events and https://shardeum.org/news have no <h1> headline, so visitors and search engines get no clear main topic.

https://shardeum.org/events has 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.

https://shardeum.org/blog, https://shardeum.org/faq, https://shardeum.org/blockchain-ebook-download, https://shardeum.org/marketing-communications, https://shardeum.org/community and https://shardeum.org/shm-token-guide and 5 others took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://shardeum.org/.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

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.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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

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

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

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

Opening the homepage sets 8 cookies (measured from a US location before any click).

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