Website review, no card needed

irishtimes.com logo

irishtimes.com website review

Visit site (opens in a new tab)Reviewed 30 October 202636 issues · 89 checks

This review found 36 issues worth fixing on irishtimes.com, 15 of them high impact, across 89 checks. The most urgent: render-blocking 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.7 s1.6 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.7 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
173 ms139 msMay 9Oct 24169 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026146 ms
May 16, 2026145 ms
May 23, 2026143 ms
May 30, 2026144 ms
Jun 6, 2026145 ms
Jun 13, 2026146 ms
Jun 20, 2026148 ms
Jun 27, 2026147 ms
Jul 4, 2026146 ms
Jul 11, 2026146 ms
Jul 18, 2026146 ms
Jul 25, 2026146 ms
Aug 1, 2026143 ms
Aug 8, 2026143 ms
Aug 15, 2026144 ms
Aug 22, 2026146 ms
Aug 29, 2026150 ms
Sep 5, 2026150 ms
Sep 12, 2026152 ms
Sep 19, 2026152 ms
Sep 26, 2026153 ms
Oct 3, 2026157 ms
Oct 10, 2026161 ms
Oct 17, 2026164 ms
Oct 24, 2026169 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 irishtimes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. irishtimes.com at 0.5 s0.5 s
  2. irishtimes.com at 1.1 s1.1 s
  3. irishtimes.com at 1.6 s1.6 s
  4. irishtimes.com at 2.2 s2.2 s
  5. irishtimes.com at 2.7 s2.7 s
  6. irishtimes.com at 3.3 s3.3 s
  7. irishtimes.com at 3.8 s3.8 s
  8. irishtimes.com at 4.4 s4.4 s

Speed

9 to fix44
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 44

    44/100

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

  • 3,809 HTML elements

    The page has 3,809 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused JavaScript

    686 KiB

    About 686 KiB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Optanon and Google/Doubleclick Ads and others), adding 1.3 MB and 542 ms of main-thread time.

  • Use efficient cache lifetimes

    627 KiB

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

  • 10 long tasks on the main thread

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

  • Main-thread work: 3.3 s

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

  • Optanon adds 117 ms

    117 ms

    Optanon costs a phone 117 ms of main-thread work and 386 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 CSS

    150 ms · 51 KiB

    About 51 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.

  • Improve image delivery

    107 KiB

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    25 KiB

    Polyfills for old browsers add 25 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: 254 ms

    254 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 8.3 s

    8.3 s

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

  • Largest Contentful Paint: 9.4 s

    9.4 s

    Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Actor Patrick Stewart, star of stage and screen, dies aged …”.

  • Time to Interactive: 23.0 s

    23.0 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • Total Blocking Time: 497 ms

    497 ms

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

  • 3 images without width and height

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

  • Tap response (INP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 146 ms to 169 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-24, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.0 s

    1.0 s

    Real visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 181 ms

    181 ms

    Real visitors wait 181 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 332 ms

    332 ms

    Real visitors wait 332 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 4.8 MB in 116 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 116 requests on a phone: scripts 1.4 MB (15), HTML 1.3 MB (2) and other files 1.0 MB (58). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    61 KiB

    1 image is downloaded at several times the size a phone draws it, for example NBZTERI3LJCBNBYCBPDZJLZMV4.png at 1,672 px wide, shown at 112 px. Resized copies would save about 61 KiB.

  • 1 image in older formats

    1 image (63 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.

  • 3 images below the first screen load straight away

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

  • About 1.4 g of CO₂ per visit

    1.36 g

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

Accessibility

5 to fixGoogle 8191
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 47 tap targets too small

    47 tap targets are too small or too close together to hit reliably with a finger.

  • 31 text elements with low contrast

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

  • Frames without titles

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

  • 9 links without text

    9 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 124 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

4 to fixGoogle 9276
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (88 characters)

    Your title is 88 characters, so Google will cut it off around 60: “The Irish Times | Latest news and headlines - Irish news, world news, video and podcasts”.

  • Meta description is long (216 characters)

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

  • 1 link with vague text

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

  • Open Graph partly set

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

  • 560 internal links, 20 external

    The homepage links to 560 pages on irishtimes.com and 20 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.irishtimes.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.irishtimes.com/arc/outboundfeeds/sitemap/.

AI search readiness

1 to fix65
  • robots.txt blocks 1 AI answer engine crawler

    1 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No llms.txt

    There is no https://www.irishtimes.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.

  • Opted out of AI training for 1 crawler

    robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

2 checks passed
  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,796 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix80
  • 7 pages point its canonical at the homepage

    https://www.irishtimes.com/crosswords-puzzles, https://www.irishtimes.com/newsletters, https://www.irishtimes.com/crosswords-puzzles/the-daily-eight, https://www.irishtimes.com/crosswords-puzzles/crosaire, https://www.irishtimes.com/crosswords-puzzles/simplex and https://www.irishtimes.com/crosswords-puzzles/sudoku and 1 other declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 5 pages without a meta description

    https://www.irishtimes.com/crosswords-puzzles/the-daily-eight, https://www.irishtimes.com/crosswords-puzzles/crosaire, https://www.irishtimes.com/crosswords-puzzles/simplex, https://www.irishtimes.com/crosswords-puzzles/sudoku and https://www.irishtimes.com/crosswords-puzzles/news-quiz have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.irishtimes.com/common-ground, https://www.irishtimes.com/newsletters, https://www.irishtimes.com/latest, https://www.irishtimes.com/crosswords-puzzles/the-daily-eight, https://www.irishtimes.com/crosswords-puzzles/crosaire and https://www.irishtimes.com/crosswords-puzzles/simplex and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.irishtimes.com/environment/climate-crisis, https://www.irishtimes.com/subscribe, https://www.irishtimes.com/crosswords-puzzles/the-daily-eight, https://www.irishtimes.com/crosswords-puzzles/crosaire and https://www.irishtimes.com/crosswords-puzzles/simplex took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 197 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

2 to fixGoogle 9687
  • 26 small tap targets

    26 of 109 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • 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: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 2,716 words of copy

    The homepage carries about 2,716 words of visible text.

3 checks passed
  • Clear next step on the first screen

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

  • 9 calls to action

    The homepage has 9 calls to action, for example “Subscribe”, “Sign up” and “Why Subscribe?”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • 19 other companies contacted

    Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 irishtimes.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Akamai

Company

Founded
1859
Headquarters
Dublin

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on irishtimes.com, including 15 speed issues, 4 SEO issues and 4 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

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