Website review, no card needed
informaconnect.com website review
Visit site (opens in a new tab)Reviewed 4 November 202646 issues · 87 checks
This review found 46 issues worth fixing on informaconnect.com, 22 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.9 s |
| Jul 25, 2026 | 5.0 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 4.8 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.3 s |
| Oct 31, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 344 ms |
| May 23, 2026 | 361 ms |
| May 30, 2026 | 366 ms |
| Jun 6, 2026 | 372 ms |
| Jun 13, 2026 | 362 ms |
| Jun 20, 2026 | 486 ms |
| Jun 27, 2026 | 504 ms |
| Jul 4, 2026 | 531 ms |
| Jul 11, 2026 | 606 ms |
| Jul 18, 2026 | 598 ms |
| Jul 25, 2026 | 624 ms |
| Aug 1, 2026 | 626 ms |
| Aug 8, 2026 | 601 ms |
| Aug 15, 2026 | 560 ms |
| Aug 22, 2026 | 503 ms |
| Aug 29, 2026 | 455 ms |
| Sep 5, 2026 | 393 ms |
| Sep 12, 2026 | 360 ms |
| Sep 19, 2026 | 354 ms |
| Sep 26, 2026 | 371 ms |
| Oct 3, 2026 | 395 ms |
| Oct 10, 2026 | 418 ms |
| Oct 17, 2026 | 416 ms |
| Oct 24, 2026 | 398 ms |
| Oct 31, 2026 | 378 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.9 s
1.9 s
2.8 s
3.8 s
4.7 s
5.7 s
6.6 s
7.6 s
Speed
Use efficient cache lifetimes
2.1 s · 4.3 MB18 files are served with short cache lifetimes, so returning visitors download them again (4.3 MB).
Reduce unused JavaScript
3.5 s · 945 KiBAbout 945 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Render-blocking requests
3.1 s22 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Google Tag Manager adds 1.5 s
1.5 sGoogle Tag Manager costs a phone 1.5 s of main-thread work and 1.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, transcend-cdn.com and Kameleoon and others), adding 1.9 MB and 2.1 s of main-thread time.
Reduce unused CSS
300 ms · 132 KiBAbout 132 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 340 ms. During a long task the page ignores taps.
1,852 HTML elements
The page has 1,852 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
192 KiB7 images could be 192 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
150 ms · 28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 60 ms
60 msYour server sent the HTML in 60 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.3 s
4.3 sReal visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.43
0.43For real visitors the layout shifts by 0.43 (75th percentile). Good is under 0.1.
Real-user FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 9.2 s
9.2 sThe first text or image appears after 9.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 25.3 s
25.3 sYour largest element takes 25.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 36.2 s
36.2 sThe page becomes fully interactive after 36.2 s. Good is under 3.8 s.
Speed Index: 15.0 s
15.0 sVisually, the page fills in at 15.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Real-user INP: 306 ms
306 msReal visitors wait 306 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 344 ms to 378 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 14.2 MB in 197 requests
14.2 MBYour homepage downloads 14.2 MB in 197 requests on a phone: images 10.7 MB (56), scripts 2.4 MB (44) and HTML 541 KiB (1). Under 2 MB keeps phones on slow connections fast.
4 images far larger than shown
152 KiB4 images are downloaded at several times the size a phone draws them, for example 202401-InformaConnect-HP-Header-Image-1-9df3bcee9f2e0c5f5c76 at 1,950 px wide, shown at 390 px. Resized copies would save about 152 KiB.
1 image below the first screen load straight away
1 image further down the page (30 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 4.0 g of CO₂ per visit
4.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.03 g of CO₂e: 483.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Hidden but focusable
8 elements hidden from screen readers can still receive keyboard focus.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
81 images without alt text
81 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (22 characters)
Your title is only 22 characters: “Home | Informa Connect”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
77 internal links, 22 external
The homepage links to 77 pages on informaconnect.com and 22 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Live events, digital content and training for professionals who want to achieve more.”.
Canonical URL set
The canonical URL is https://informaconnect.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://informaconnect.com/sitemap.xml.
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.
No llms.txt
There is no https://informaconnect.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,461 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://informaconnect.com/about-us, https://informaconnect.com/our-story, https://informaconnect.com/careers and https://informaconnect.com/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://informaconnect.com/informa-real-estate, whose canonical is https://informaconnect.com/real-estate-group. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages without an H1
https://informaconnect.com/about-us, https://informaconnect.com/our-story, https://informaconnect.com/marketing-solutions, https://informaconnect.com/careers and https://informaconnect.com/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
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.
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.
Thin social proof
Social proof on the homepage: 11 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
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 786 words of copy
The homepage carries about 786 words of visible text.
1 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact Us”.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Clarity and The Trade Desk (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.
23 cookies set on arrival
23Opening the homepage sets 23 cookies, 1 of them by other companies (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.
35 other companies contacted
Loading the homepage contacts 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 informaconnect.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
- Fastly
Hiring
- Hiring
- 144 open roles
- Teams
- Informa TechTarget (15), inD (1), Legacy Ascential (Workday) (1)
- Job board
- smartrecruiters
- Careers page
- informaconnect.com/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on informaconnect.com, including 22 speed issues, 3 SEO issues and 6 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.