eventnetwork.com website review

Not measured in this review.

• Tap response (INP) held steady for real visitors

  +8%

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

• Page weight: 5.1 MB

  5.1 MB

  Your homepage downloads 5.1 MB on a phone, 3.0 MB of it images (59%). Under 2 MB keeps phones on slow connections fast.

• 2 images below the first screen load straight away

  2 images further down the page (198 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (2)

• About 1.4 g of CO₂ per visit

  1.45 g

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

• 1 text element with low contrast

  1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (1)

• Heading levels should only increase by one (3 elements)

  Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• No meta description

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

  View source

• Title is short (12 characters)

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

  View source

• Structured data has 2 problems

  Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/64cc776d3c2fa442ee9…”.

  View source

• Open Graph partly set

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

  View source

• 73 internal links, 0 external

  The homepage links to 73 pages on eventnetwork.com and 0 external pages.

• Most text only appears after JavaScript runs

  29%

  A phone browser shows 468 words, but the HTML your server sends has only 135. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

• Organization data is thin (0 of 6 facts)

  Your Organization JSON-LD is missing name, url, 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.

  View source

• No llms.txt

  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.

• 15 pages without a meta description

  /who-we-are, /what-we-do, /partnerships/aquariums, /partnerships/art, /partnerships/gardens and /partnerships/leisure-hospitality and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (8)

• 1 page without an H1

  /partnerships/dr has no <h1> headline, so visitors and search engines get no clear main topic.

• 2 pages with very little text

  /partnerships/leisure-hospitality and /partnerships/zoos have 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.

• 15 internal pages checked

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

• 4 JavaScript errors while loading

  4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

• 1 broken link to your own pages

  1 link from your homepage to your own site is broken, for example https://www.eventnetwork.com/partnerships-folder/ (404).

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• Short HSTS lifetime

  HSTS is set, but max-age is 180 days; one year is the recommended minimum.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  eventnetwork.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  eventnetwork.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

• 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 form on the homepage

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

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• 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 468 words of copy

  The homepage carries about 468 words of visible text.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be eventnetwork.com is still delivered. Reports are on, so moving to quarantine is the next step.

• Email authentication score: 70/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 1 tracker load before any consent

  1

  Before a visitor clicks anything, the page loads 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.

• 3 cookies set on arrival

  3

  Opening the homepage sets 3 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.

• 12 other companies contacted

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