Website review, no card needed
ieiworld.com website review
Visit site (opens in a new tab)Reviewed 30 October 202648 issues · 70 checks
This review found 48 issues worth fixing on ieiworld.com, 20 of them high impact, across 70 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.1 s |
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.6 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.1 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.5 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.6 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 4.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 124 ms |
| May 16, 2026 | 126 ms |
| May 23, 2026 | 124 ms |
| May 30, 2026 | 131 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 139 ms |
| Jun 27, 2026 | 130 ms |
| Jul 4, 2026 | 125 ms |
| Jul 11, 2026 | 123 ms |
| Jul 18, 2026 | 124 ms |
| Jul 25, 2026 | 126 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 143 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 156 ms |
| Aug 29, 2026 | 151 ms |
| Sep 5, 2026 | 148 ms |
| Sep 12, 2026 | 140 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 141 ms |
| Oct 3, 2026 | 140 ms |
| Oct 10, 2026 | 140 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 140 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.1 s
2.7 s
3.2 s
3.7 s
4.3 s
Speed
Improve image delivery
3.0 s · 6.9 MB28 images could be 6.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Use efficient cache lifetimes
1.0 s · 3.0 MB168 files are served with short cache lifetimes, so returning visitors download them again (3.0 MB).
Render-blocking requests
2.4 s35 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and ptengine.com and others), adding 1.0 MB and 1.3 s of main-thread time.
Avoid multiple page redirects
758 msThe page goes through 1 redirect before it starts loading, costing about 758 ms. Link and advertise the final URL directly.
Google Tag Manager adds 618 ms
618 msGoogle Tag Manager costs a phone 618 ms of main-thread work and 537 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.
Reduce unused JavaScript
369 KiBAbout 369 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Facebook adds 273 ms
273 msFacebook costs a phone 273 ms of main-thread work and 249 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.
2,201 HTML elements
The page has 2,201 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 177 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 10 KiB10 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 3 KiB3 KiB could be saved by minifying CSS.
Legacy JavaScript
35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 149 ms
149 msYour server sent the HTML in 149 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 4.5 s
4.5 sReal visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.1 s
4.1 sReal visitors see the first content after 4.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 40.5 s
40.5 sYour largest element takes 40.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 47.3 s
47.3 sThe page becomes fully interactive after 47.3 s. Good is under 3.8 s.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 551 ms
551 msScripts block taps and scrolling for 551 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 124 ms to 140 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-10-24, real Chrome visitors' largest content (lcp) went from 4.1 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 135 ms
135 msReal visitors wait 135 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 17.9 MB in 252 requests
17.9 MBYour homepage downloads 17.9 MB in 252 requests on a phone: images 15.6 MB (123), scripts 1.2 MB (41) and fonts 947 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 5.1 g of CO₂ per visit
5.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.07 g of CO₂e: 608.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links do not have a discernible name
Links do not have a discernible name (8 elements).
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
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
No XML sitemap at https://www.ieiworld.com/_sitemap_xml/, so Google discovers your pages only by following links.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1 checks passed
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No Organization structured data
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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
llms.txt published
The site publishes https://www.ieiworld.com/llms.txt (7 KiB, 24 links), a plain-text guide to the site for AI tools.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
3 console errors
3 errors were logged to the browser console during Google's test (“Loading the image 'https://onetag-sys.com/match/?int_id=30&uid=&gdpr=0&gdpr_consent=&us_privacy=' v…”).
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 0 words
The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ieiworld.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- CloudFront
Company
- Employees
- 24
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on ieiworld.com, including 22 speed issues, 9 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.