Website review, no card needed

harkins.com logo

harkins.com website review

Visit site (opens in a new tab)Reviewed 11 October 202637 issues · 71 checks

This review found 37 issues worth fixing on harkins.com, 14 of them high impact, across 71 checks. The most urgent: improve image delivery. 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.7 s1.6 sApr 18Oct 32.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.6 s
Apr 25, 20262.5 s
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.4 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.3 s
Jul 25, 20262.0 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20262.2 s
Sep 12, 20262.4 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
124 ms91 msApr 18Oct 3120 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026117 ms
Apr 25, 2026118 ms
May 2, 2026117 ms
May 9, 2026114 ms
May 16, 2026113 ms
May 23, 2026112 ms
May 30, 2026112 ms
Jun 6, 2026112 ms
Jun 13, 2026115 ms
Jun 20, 2026116 ms
Jun 27, 2026119 ms
Jul 4, 2026120 ms
Jul 11, 2026120 ms
Jul 18, 2026115 ms
Jul 25, 2026107 ms
Aug 1, 202696 ms
Aug 8, 202695 ms
Aug 15, 202695 ms
Aug 22, 202696 ms
Aug 29, 2026103 ms
Sep 5, 2026111 ms
Sep 12, 2026113 ms
Sep 19, 2026119 ms
Sep 26, 2026120 ms
Oct 3, 2026120 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 harkins.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. harkins.com at 0.8 s0.8 s
  2. harkins.com at 1.5 s1.5 s
  3. harkins.com at 2.3 s2.3 s
  4. harkins.com at 3.0 s3.0 s
  5. harkins.com at 3.8 s3.8 s
  6. harkins.com at 4.5 s4.5 s
  7. harkins.com at 5.3 s5.3 s
  8. harkins.com at 6.0 s6.0 s

Speed

11 to fix40
  • Improve image delivery

    1.7 s · 1.5 MB

    29 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

  • Reduce unused JavaScript

    1.4 s · 378 KiB

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

  • Mobile performance score: 40

    40/100

    Your mobile performance score is 40 (desktop: 34). 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, Optanon and Google/Doubleclick Ads and others), adding 3.7 MB and 770 ms of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 172 KiB

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

  • Google Tag Manager adds 675 ms

    675 ms

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

  • Legacy JavaScript

    400 ms · 22 KiB

    Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • Main-thread work: 3.6 s

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

  • 14 long tasks on the main thread

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

  • imgix adds 0 ms

    0 ms

    imgix costs a phone 0 ms of main-thread work and 3.0 MB 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.

  • 1,893 HTML elements

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

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Font display

    50 ms

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

  • Reduce unused CSS

    34 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

9 to fix33
  • 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 CLS: 1.57

    1.57

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

  • Largest Contentful Paint: 20.4 s

    20.4 s

    Your largest element takes 20.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Other Mommy - background image”.

  • Time to Interactive: 29.8 s

    29.8 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Total Blocking Time: 911 ms

    911 ms

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.158

    0.158

    The layout shifts by 0.158 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

4 checks passed
  • Real-user INP: 146 ms

    146 ms

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

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

  • Real-user TTFB: 460 ms

    460 ms

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix70
  • Page weight: 5.9 MB in 187 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 187 requests on a phone: images 3.1 MB (57), other files 1.4 MB (47) and scripts 1.4 MB (80). Under 2 MB keeps phones on slow connections fast.

  • About 1.7 g of CO₂ per visit

    1.67 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 9798
  • 15 text elements with low contrast

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

7 to fixGoogle 8375
  • Title is short (23 characters)

    Your title is only 23 characters: “Harkins Theatres | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 36 links crawlers can't follow

    36 links have no real href, so search engines can't follow them.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (27 characters)

    Your meta description is only 27 characters: “Homepage | Harkins Theatres”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

  • 9 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

4 checks passed
  • One H1 headline

    Your main headline reads: “Harkins Theatres”.

  • 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://cmsservice.harkins.com/api/v1/sitemap/index.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    1%

    A phone browser shows 179 words, but the HTML your server sends has only 2. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://harkins.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.

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

Best practices

2 to fixGoogle 9691
  • 16 small tap targets

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

  • 24 distorted images

    24 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 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 179 words

    The homepage has only about 179 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.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Close app download banner”.

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 10 other companies contacted

    Loading the homepage contacts 10 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 harkins.com, 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 37 issues on harkins.com, including 20 speed issues, 7 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