iwedglobal.com website review

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

4 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (mycourse.app, Google Tag Manager and Stripe and others), adding 14.5 MB and 1.3 s of main-thread time.

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

About 375 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

mycourse.app costs a phone 451 ms of main-thread work and 5.7 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.

Vimeo costs a phone 133 ms of main-thread work and 7.5 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.

Google Tag Manager costs a phone 302 ms of main-thread work and 561 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

13 KiB could be saved by minifying CSS.

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.

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

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

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

Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Wedding & Event Industry's Best and Brightest Choose IW…”.

Scripts block taps and scrolling for 544 ms in total while the page loads. Good is under 200 ms.

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

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 15.2 MB in 212 requests on a phone: other files 6.6 MB (54), images 4.4 MB (15) and scripts 3.3 MB (108). Under 2 MB keeps phones on slow connections fast.

1 image (30 KiB) is 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 4.31 g of CO₂e: 517.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

12 buttons have no accessible name, so screen readers announce just “button”.

22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 frames have no title, so screen-reader users cannot tell what they contain.

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your page has no <title>, so Google has to invent the blue link in search results.

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

There are 2 <h1> headlines (“The Wedding & Event Industry's Best and Brightest…” and “PRIVATE & CORPORATE EVENT DESIGN TRAINING”). One clear main headline is easier for people and search engines.

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

11 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 30 pages on iwedglobal.com and 7 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://iwedglobal.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://iwedglobal.com/event-designer-boot-camp has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

Chrome logged issues while loading the page (“Cookie”).

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.

Social proof on the homepage: “25,000+ STUDENTS”. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

The homepage carries about 874 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag 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.

Opening the homepage sets 28 cookies, 2 of them by other companies (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 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.