Website review, no card needed

hilltimes.com logo

hilltimes.com website review

Visit site (opens in a new tab)Reviewed 19 October 202643 issues · 92 checks

This review found 43 issues worth fixing on hilltimes.com, 18 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
2.9 s1.3 sApr 25Oct 101.9 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.7 s
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.6 s
May 23, 20262.5 s
May 30, 20262.7 s
Jun 6, 20262.5 s
Jun 13, 20262.2 s
Jun 20, 20261.8 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.6 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.7 s
Aug 8, 20261.6 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
116 ms84 msApr 25Oct 1088 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202695 ms
May 2, 202697 ms
May 9, 202698 ms
May 16, 2026100 ms
May 23, 2026102 ms
May 30, 2026105 ms
Jun 6, 2026104 ms
Jun 13, 2026105 ms
Jun 20, 2026105 ms
Jun 27, 2026103 ms
Jul 4, 2026101 ms
Jul 11, 202696 ms
Jul 18, 202694 ms
Jul 25, 202695 ms
Aug 1, 202696 ms
Aug 8, 2026103 ms
Aug 15, 2026105 ms
Aug 22, 2026109 ms
Aug 29, 2026112 ms
Sep 5, 2026112 ms
Sep 12, 2026112 ms
Sep 19, 2026109 ms
Sep 26, 2026103 ms
Oct 3, 202692 ms
Oct 10, 202688 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 hilltimes.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hilltimes.com at 1.4 s1.4 s
  2. hilltimes.com at 2.7 s2.7 s
  3. hilltimes.com at 4.1 s4.1 s
  4. hilltimes.com at 5.5 s5.5 s
  5. hilltimes.com at 6.9 s6.9 s
  6. hilltimes.com at 8.2 s8.2 s
  7. hilltimes.com at 9.6 s9.6 s
  8. hilltimes.com at 11.0 s11.0 s

Speed

13 to fix26
  • Reduce unused JavaScript

    14.2 s · 1.4 MB

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

  • Use efficient cache lifetimes

    5.5 s · 1.0 MB

    50 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

  • Render-blocking requests

    4.0 s

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

  • Google/Doubleclick Ads adds 2.4 s

    2.4 s

    Google/Doubleclick Ads costs a phone 2.4 s of main-thread work and 3.6 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.

  • Google Tag Manager adds 1.3 s

    1.3 s

    Google Tag Manager costs a phone 1.3 s of main-thread work and 497 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.

  • Main-thread work: 13.0 s

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

  • Mobile performance score: 26

    26/100

    Your mobile performance score is 26 (desktop: 54). 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/Doubleclick Ads, Google Tag Manager and Google CDN and others), adding 5.4 MB and 5.3 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Google CDN adds 696 ms

    696 ms

    Google CDN costs a phone 696 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.

  • Facebook adds 445 ms

    445 ms

    Facebook costs a phone 445 ms of main-thread work and 224 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

    300 ms · 75 KiB

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

  • 2,196 HTML elements

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

  • Minify JavaScript

    240 ms · 35 KiB

    35 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    201 KiB

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

  • Duplicated JavaScript

    150 ms · 24 KiB

    24 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    90 ms · 3 KiB

    3 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

  • Legacy JavaScript

    12 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 54 but mobile only 26. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 29 ms

    29 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 37.4 s

    37.4 s

    Your largest element takes 37.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Be the first to know of any new directives affecting public…”.

  • Speed Index: 16.0 s

    16.0 s

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

  • Time to Interactive: 37.7 s

    37.7 s

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

  • Total Blocking Time: 4.1 s

    4.1 s

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

  • First Contentful Paint: 6.0 s

    6.0 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

    Real visitors wait 1.1 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) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 95 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 113 ms

    113 ms

    Real visitors wait 113 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: 1.5 s

    1.5 s

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

  • Largest content (LCP) got 29% faster for real visitors

    -29%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 6.9 MB in 207 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 207 requests on a phone: scripts 2.9 MB (74), images 2.7 MB (26) and fonts 628 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (72 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    1.95 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8390
  • 12 text elements with low contrast

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

  • 5 images without alt text

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

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

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

  • 82 links without text

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

  • No main landmark

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

  • 3 form fields without a label

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

  • 3 tap targets too small

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 7784
  • Meta description is short (55 characters)

    Your meta description is only 55 characters: “THE LATEST POLITICS THIS MORNING, OPINION & COLUMNISTS.”. 70 to 160 characters is enough to sell the click.

  • 97 H1 headlines

    There are 97 <h1> headlines (“Lobbyists push for tax changes in hydrogen produc…”, “‘There’s a danger in removing transparency’ amid …” and “‘Late to the party’ or ‘asleep at the switch’? Ca…”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, NewsArticle, Organization and Person) but with 1 problem, for example “Person: missing name”.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 528 internal links, 25 external

    The homepage links to 528 pages on hilltimes.com and 25 external pages.

5 checks passed
  • Title: 41 characters

    Your title is a healthy 41 characters: “People. Policy. Politics - The Hill Times”.

  • Canonical URL set

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

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.hilltimes.com/sitemap.xml.

AI search readiness

1 to fix65
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-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.hilltimes.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 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, 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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix85
  • 4 pages without a meta description

    https://www.hilltimes.com/policy, https://www.hilltimes.com/public-service, https://www.hilltimes.com/issue and https://www.hilltimes.com/get-a-subscription have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.hilltimes.com/civil-circles, whose canonical is https://www.hilltimes.com/category/ht-columns/civil-circles. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.hilltimes.com/get-a-subscription has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.hilltimes.com/get-a-subscription has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 190 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 9287
  • 19 small tap targets

    19 of 51 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 “Uncaught TypeError: $(...).autocomplete is not a function”.

  • 1 low-resolution image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • About 3,190 words of copy

    The homepage carries about 3,190 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 20 calls to action

    The homepage has 20 calls to action, for example “Subscribe”, “Contact Us” and “Subscribe Now”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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
  • 4 trackers load before any consent

    4

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

  • 15 cookies set on arrival

    15

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

  • 24 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager

Company

Founded
1989
Headquarters
Ottawa

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on hilltimes.com, including 21 speed issues, 4 SEO issues and 2 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