thenectarfestival.com website review

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

The page has 1,904 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Hexton costs a phone 15 ms of main-thread work and 310 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.

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

4 third-party services load with your homepage (Shopify, Hexton and nfcube.com and others), adding 397 KiB and 40 ms of main-thread time.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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 3.3 MB in 204 requests on a phone: images 2.1 MB (84), other files 623 KiB (60) and scripts 527 KiB (43). Under 2 MB keeps phones on slow connections fast.

2026_nectar_festival_may16_web_slide.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example nectar_festival_2025_logo_vertical_colour.png at 1,104 px wide, shown at 50 px. Resized copies would save about 82 KiB.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

The homepage links to 55 pages on thenectarfestival.com and 5 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://thenectarfestival.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://thenectarfestival.com/pages/music-artists, https://thenectarfestival.com/pages/event-schedule-2026, https://thenectarfestival.com/pages/the-sunset-stage-artists, https://thenectarfestival.com/pages/night-garden, https://thenectarfestival.com/pages/abstrakt-sonance-the-nectar-orchestra and https://thenectarfestival.com/pages/co-create and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://thenectarfestival.com/apps/FAQs, whose canonical is https://thenectarfestival.com/apps/faqs. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://thenectarfestival.com/pages/the-sunset-stage-artists, https://thenectarfestival.com/pages/night-garden, https://thenectarfestival.com/pages/abstrakt-sonance-the-nectar-orchestra and https://thenectarfestival.com/pages/co-create have no <h1> headline, so visitors and search engines get no clear main topic.

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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.

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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.