nourishwithsim.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 9.7 MB and 319 ms of main-thread time.

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

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

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

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

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

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

About 146 KiB of JavaScript is downloaded but never used on this page.

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

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

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.

3 KiB could be saved by minifying CSS.

Your largest element takes 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “4/4 Weightloss Challenge Lose Upto 4kgs In 4 Weeks Limited …”.

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

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

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

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

Your homepage downloads 19.4 MB in 360 requests on a phone: images 17.4 MB (94), other files 1.0 MB (188) and scripts 738 KiB (66). Under 2 MB keeps phones on slow connections fast.

3 images weigh 11.8 MB together. On a phone connection a single image that size takes seconds.

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

5 images (11.9 MB) 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 5.49 g of CO₂e: 659.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

ARIA input fields must have an accessible name: 6 elements on the page fail this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

1 element hidden from screen readers can still receive keyboard focus.

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

6 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 (h1 → h3), which makes the page harder to scan with a screen reader.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 8 <h1> headlines (“Simrun Chopra”, “4/4 Weightloss Challenge” and “On Our Programs you Could”). One clear main headline is easier for people and search engines.

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

No XML sitemap at https://nourishwithsim.com/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 99 pages on nourishwithsim.com and 8 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 https://nourishwithsim.com/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://nourishwithsim.com/pages/one-to-one and https://nourishwithsim.com/blogs/blog have no meta description, so Google writes the search snippet from whatever text it finds.

https://nourishwithsim.com/blogs/sims-inner-circle-recipes/pcos has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://nourishwithsim.com/Liquid%20error%20(sections/home-sec11-nws%20line%2055):%20invalid%20url%20input.

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

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

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 2,287 words of visible text.

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