datasembly.com website review

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

About 713 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

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

Your mobile performance score is 54 (desktop: 51). Pages that score under 90 lose visitors before the first paint.

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

8 third-party services load with your homepage (Google Tag Manager, Hubspot and LinkedIn Ads and others), adding 1.4 MB and 543 ms of main-thread time.

Google Tag Manager costs a phone 285 ms of main-thread work and 1,011 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.

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

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

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

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

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

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.

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

Your largest element takes 27.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies on our website to give you the most relevant…”.

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

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

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

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.

Your homepage downloads 5.3 MB in 195 requests on a phone: fonts 1.8 MB (18), images 1.7 MB (77) and scripts 1.5 MB (37). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example Dots-logo.svg at 298 px wide, shown at 93 px. Resized copies would save about 32 KiB.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 33 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.

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

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

The homepage links to 43 pages on datasembly.com and 5 external pages.

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.

/grocery-price-index and /blogs all use the title “Real-time, local data for pricing and promotions | Datasembly | Blogs”. Search engines can't tell which page to show for a search, so each competes with the others.

/news has no meta description, so Google writes the search snippet from whatever text it finds.

/grocery-price-index and /blogs use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /grocery-price-index, whose canonical is /blogs. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/grocery-price-index has no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

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

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

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

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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,028 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, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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