mariamkhan.one website review

3 images could be 841 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.

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

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

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

6 third-party services load with your homepage (Squarespace, Google Tag Manager and sqspcdn.com and others), adding 2.6 MB and 775 ms of main-thread time.

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

About 138 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.

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

Squarespace costs a phone 439 ms of main-thread work and 973 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.

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.0 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

Your largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mariam Khan→ product designer and strategist who creates co…”.

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

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

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

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

1 image 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 2.8 MB in 65 requests on a phone: scripts 1.3 MB (39), images 1.0 MB (7) and stylesheets 163 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 11 characters: “Mariam Khan”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5fc9e845254c5916e12…”.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 38 pages on mariamkhan.one and 6 external pages.

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.

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.

/about, /archive and /mwho have no meta description, so Google writes the search snippet from whatever text it finds.

/archive and /mwho have no <h1> headline, so visitors and search engines get no clear main topic.

/archive 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.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/5fc9e845254c5916e12776a6/91/5c5a…”.

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.

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

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

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