eventsbysmaya.com website review

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

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

About 52 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Premium wedding & event design for every ritual, celebratio…”. Most of its time is element render delay (4.3 s).

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

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

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 22.0 MB in 46 requests on a phone: media 20.4 MB (2), images 1.3 MB (6) and scripts 236 KiB (15). Under 2 MB keeps phones on slow connections fast.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Headings skip levels (h2 → h4), 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.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

There is no robots.txt at eventsbysmaya.com/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 24 pages on eventsbysmaya.com and 2 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://eventsbysmaya.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.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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

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.