makeblock.com website review

Google Tag Manager costs a phone 1.1 s of main-thread work and 854 KiB 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.

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

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

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

Shopify costs a phone 475 ms of main-thread work and 32.8 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.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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

Klaviyo costs a phone 206 ms of main-thread work and 357 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.

atomm.com costs a phone 35 ms of main-thread work and 488 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.

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

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need.

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

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

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

Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MO.jpg__PID:49925cbb-8c25-49e1-a57f-fb65fc54d9c9”.

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

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

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

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

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

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

Your homepage downloads 36.4 MB in 429 requests on a phone: media 28.6 MB (5), images 3.8 MB (81) and scripts 2.7 MB (190). Under 2 MB keeps phones on slow connections fast.

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

1 image (84 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.

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“Makeblock” and “Makeblock STEAM Education Solution”). One clear main headline is easier for people and search engines.

Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: missing name”.

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

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

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

The homepage links to 187 pages on makeblock.com and 33 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.makeblock.com/.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Requests the notification permission on page load.

2 links to other sites are dead, for example https://www.youtube.com/@Makeblock (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

makeblock.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

makeblock.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 3 trust badges. 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 carries about 800 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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.

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