Website review, no card needed

innovate.ie logo

innovate.ie website review

Visit site (opens in a new tab)Reviewed 23 October 202633 issues · 79 checks

This review found 33 issues worth fixing on innovate.ie, 11 of them high impact, across 79 checks. The most urgent: page weight: 27.0 MB in 106 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.1 s824 msMay 2Oct 10858 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026887 ms
May 9, 2026956 ms
May 30, 20261.1 s
Jun 20, 2026948 ms
Jun 27, 2026967 ms
Jul 4, 20261.0 s
Jul 11, 20261.1 s
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Sep 12, 20261.0 s
Oct 10, 2026858 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

Full-page screenshot of innovate.ie (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. innovate.ie at 0.8 s0.8 s
  2. innovate.ie at 1.7 s1.7 s
  3. innovate.ie at 2.5 s2.5 s
  4. innovate.ie at 3.4 s3.4 s
  5. innovate.ie at 4.2 s4.2 s
  6. innovate.ie at 5.1 s5.1 s
  7. innovate.ie at 5.9 s5.9 s
  8. innovate.ie at 6.8 s6.8 s

Speed

11 to fix49
  • Render-blocking requests

    2.4 s

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

  • Intercom adds 1.4 s

    1.4 s

    Intercom costs a phone 1.4 s of main-thread work and 972 KiB 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: 49

    49/100

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

  • Main-thread work: 6.7 s

    A phone's processor spends 6.7 s on main-thread work while loading, 4.3 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 (Intercom, Google Tag Manager and Google CDN and others), adding 2.5 MB and 3.2 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 1.2 MB

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

  • Google Tag Manager adds 605 ms

    605 ms

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

  • Google CDN adds 544 ms

    544 ms

    Google CDN costs a phone 544 ms of main-thread work and 733 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.

  • Improve image delivery

    603 KiB

    11 images could be 603 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • posthog.com adds 430 ms

    430 ms

    posthog.com costs a phone 430 ms of main-thread work and 219 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.

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    150 KiB

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

  • Duplicated JavaScript

    45 KiB

    45 KiB JavaScript is shipped twice across bundles.

  • Reduce unused CSS

    33 KiB

    About 33 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    27 KiB

    Polyfills for old browsers add 27 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.

1 checks passed
  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix53
  • Time to Interactive: 25.9 s

    25.9 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • Largest Contentful Paint: 3.9 s

    3.9 s

    Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Since 2005, we have been accelerating digital transformatio…”.

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 18 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Cumulative Layout Shift: 0.021

    0.021

    The layout barely moves while loading (CLS 0.021, good is under 0.1).

Images and page weight

3 to fix50
  • Page weight: 27.0 MB in 106 requests

    27.0 MB

    Your homepage downloads 27.0 MB in 106 requests on a phone: media 22.7 MB (2), scripts 2.4 MB (32) and images 1.3 MB (44). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (983 KiB) are 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.

  • 1 image far larger than shown

    47 KiB

    1 image is downloaded at several times the size a phone draws it, for example Untitled-design-8.png at 1,080 px wide, shown at 153 px. Resized copies would save about 47 KiB.

  • 2 images below the first screen load straight away

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

  • About 7.6 g of CO₂ per visit

    7.64 g

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

Accessibility

6 to fixGoogle 8290
  • 6 buttons without a name

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

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

  • 13 images without alt text

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

  • All page content should be contained by landmarks (25 elements)

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 8598
  • 8 links with vague text

    8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 71 internal links, 11 external

    The homepage links to 71 pages on innovate.ie and 11 external pages.

8 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “INNOVATE is Ireland's top IT outsourcing service provider. Managed IT & IT support solutions to empower digital transfo…”.

  • One H1 headline

    Your main headline reads: “Empowering Digital Transformation Through Innovative Business IT Solutions”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Managed IT & IT Support Solutions | Innovate”.

  • Canonical URL set

    The canonical URL is https://www.innovate.ie/.

  • Structured data in place

    Structured data found: WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://www.innovate.ie/sitemaps.xml.

AI search readiness

1 to fix88
  • 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://www.innovate.ie/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,003 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.innovate.ie/contact-us has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.innovate.ie/contact-us and https://www.innovate.ie/skillsource-2 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 31 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    43 of 51 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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.

  • About 963 words of copy

    The homepage carries about 963 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact Us”, “Learn More” and “Learn more”.

  • Social proof on the page

    Social proof on the homepage: 58 testimonial or review blocks and 2 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and PostHog.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Microsoft Clarity (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.

  • 10 cookies set on arrival

    10

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

  • 21 other companies contacted

    Loading the homepage contacts 21 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 innovate.ie, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on innovate.ie, including 17 speed issues, 1 SEO issue and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25