marsdd.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 1.1 MB and 979 ms of main-thread time.

Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

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

Google Tag Manager costs a phone 694 ms of main-thread work and 708 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 123 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

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

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.

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

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

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

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

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

23 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-24, real Chrome visitors' tap response (inp) went from 111 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.5 MB in 74 requests on a phone: scripts 1.4 MB (30), media 1.3 MB (2) and images 897 KiB (21). Under 2 MB keeps phones on slow connections fast.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 23 characters: “MaRS Discovery District”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 87 pages on marsdd.com and 64 external pages.

https://www.marsdd.com/francais has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.marsdd.com/startups, https://www.marsdd.com/accelerators, https://www.marsdd.com/startups/capital-program and https://www.marsdd.com/service/momentum took over 3 s to send their HTML from our server.

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

10 of 15 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”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 994 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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 7 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.