nomaprojects.com website review

Not measured in this review.

• Real-user FCP: 2.2 s

  2.2 s

  Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

• Tap response (INP) held steady for real visitors

  +7%

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

• Largest content (LCP) held steady for real visitors

  -2%

  Over the last 25 four-week periods to 2026-11-07, 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).

• Page weight: 9.8 MB

  9.8 MB

  Your homepage downloads 9.8 MB on a phone, 4.3 MB of it images (43%). Under 2 MB keeps phones on slow connections fast.

• 30 images below the first screen load straight away

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

  Elements (5)

• 4 images far larger than shown

  316 KiB

  4 images are downloaded at several times the size a phone draws them, for example NP_LS_MG_01_a97623f5-28c2-48af-b734-c0f14f84951c.jpg at 900 px wide, shown at 237 px. Resized copies would save about 316 KiB.

  Elements (4)

• About 2.8 g of CO₂ per visit

  2.78 g

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

• Malformed lists

  Some lists contain elements other than list items, which screen readers announce wrongly.

  Elements (3)

• ARIA commands must have an accessible name (1 element)

  ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• 41 images without alt text

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

  View sourceElements (3)

• All page content should be contained by landmarks (6 elements)

  All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 76 form fields without a label

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

  View source

• 2 links without text

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

  Elements (3)

• Headings skip levels

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

  View sourceElements (2)

• 5 H1 headlines

  There are 5 <h1> headlines (“A taste of noma”, “@media (min-width: 768px) { .heading-heading_pTG3…” and “From the noma kitchen to yours”). One clear main headline is easier for people and search engines.

  View source

• Meta description is long (164 characters)

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

  View source

• 308 internal links, 18 external

  The homepage links to 308 pages on nomaprojects.com and 18 external pages.

• No llms.txt

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

• 4 pages share a meta description

  https://nomaprojects.com/blogs/journal, https://nomaprojects.com/blogs/recipes, https://nomaprojects.com/collections/staples-and-bundles and https://nomaprojects.com/collections/in-person-events use the same meta description. A description written for each page earns more clicks.

• 5 pages without an H1

  https://nomaprojects.com/collections, https://nomaprojects.com/pages/noma-projects, https://nomaprojects.com/collections/staples-and-bundles, https://nomaprojects.com/collections/books-and-merch and https://nomaprojects.com/collections/in-person-events have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 6 JavaScript errors while loading

  6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'offsetHeight')”.

• Local business without LocalBusiness data

  Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  View source

• No phone number on the homepage

  A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

• A 52-field form

  Your longest form asks for 52 fields (0 required). Every extra field lowers completion.

  View source

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• No opening hours

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

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• About 1,402 words of copy

  The homepage carries about 1,402 words of visible text.

• 7 trackers load before any consent

  7

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

• 28 cookies set on arrival

  28

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

• No consent tool detected

  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.

• 60 other companies contacted

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