Website review, no card needed

hirschsecure.com logo

hirschsecure.com website review

Visit site (opens in a new tab)Reviewed 30 October 202624 issues · 104 checks

This review found 24 issues worth fixing on hirschsecure.com, 5 of them high impact, across 104 checks. The most urgent: page weight: 5.9 MB in 139 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
2.2 s1.6 sMay 9Oct 241.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20262.0 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
158 ms117 msMay 9Oct 24129 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026125 ms
May 16, 2026137 ms
May 23, 2026139 ms
May 30, 2026131 ms
Jun 6, 2026137 ms
Jun 13, 2026132 ms
Jun 20, 2026134 ms
Jun 27, 2026141 ms
Jul 4, 2026137 ms
Jul 11, 2026131 ms
Jul 18, 2026128 ms
Jul 25, 2026128 ms
Aug 1, 2026129 ms
Aug 8, 2026150 ms
Aug 15, 2026147 ms
Aug 22, 2026137 ms
Aug 29, 2026145 ms
Sep 5, 2026139 ms
Sep 12, 2026153 ms
Sep 19, 2026150 ms
Sep 26, 2026145 ms
Oct 3, 2026138 ms
Oct 10, 2026122 ms
Oct 17, 2026129 ms
Oct 24, 2026129 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

Live view · interaction off

Speed

8 to fix67
  • Reduce unused JavaScript

    450 ms · 837 KiB

    About 837 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, insent.ai and Facebook and others), adding 1.7 MB and 1.1 s of main-thread time.

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    463 KiB

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

  • Google Tag Manager adds 398 ms

    398 ms

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

  • Main-thread work: 4.0 s

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

  • insent.ai adds 319 ms

    319 ms

    insent.ai costs a phone 319 ms of main-thread work and 613 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.

  • Render-blocking requests

    350 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

  • 18 long tasks on the main thread

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

  • Legacy JavaScript

    38 KiB

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

  • Reduce unused CSS

    38 KiB

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

  • Improve image delivery

    10 KiB

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

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

    7 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 20.5 s

    20.5 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Speed Index: 7.4 s

    7.4 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 1 image without width and height

    1 image 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-24, real Chrome visitors' tap response (inp) went from 125 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -6%

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

8 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.7 s

    1.7 s

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

  • Real-user INP: 128 ms

    128 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 492 ms

    492 ms

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

  • Cumulative Layout Shift: 0.065

    0.065

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

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “For leaders who value protection without complexity, Hirsch…”.

Images and page weight

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

    5.9 MB

    Your homepage downloads 5.9 MB in 139 requests on a phone: media 3.2 MB (3), scripts 2.4 MB (56) and other files 121 KiB (53). Under 2 MB keeps phones on slow connections fast.

  • About 1.7 g of CO₂ per visit

    1.68 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.68 g of CO₂e: 202.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

2 to fixGoogle 9797
  • 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.

  • 89 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 46 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: 46 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 12 internal links, 18 external

    The homepage links to 12 pages on hirschsecure.com and 18 external pages.

8 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Discover Hirsch's enterprise security solutions for access control, video, intrusion, and identity management for globa…”.

  • One H1 headline

    Your main headline reads: “Unified Security.Limitless Possibilities.”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “Enterprise Security Solutions | Hirsch”.

  • Canonical URL set

    The canonical URL is https://www.hirschsecure.com/us/en-us.

  • Structured data in place

    Structured data found: WebPage.

  • 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.hirschsecure.com/usa-sitemap.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 /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 (571 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 1 linked page hidden from search

    /us/en-us/privacy-policy is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 4 pages share a meta description

    /us/en-us/contact-us, /us/en-us/privacy-policy, /us/en-us/terms-of-service and /us/en-us/cookie-policy use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    /us/en-us/contact-us and /us/en-us/news-and-insights have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    /us/en-us/news-and-insights 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.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

1 to fix93
  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No clickjacking protection

    Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

  • 3 redirects before the homepage

    Opening https://hirschsecure.com goes through 3 redirects before the homepage loads.

  • 3 links through redirect chains

    3 links go through two or more redirects, for example https://hirsch-website.vercel.app/us/en/case-studies/sun-health-case-study.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

6 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (hirschsecure.com).

  • Valid certificate (88 days left)

    The certificate from Let's Encrypt · YR1 verifies for hirschsecure.com and is valid for another 88 days.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://hirschsecure.com redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 27 links work

    All 27 links checked from your homepage (9 internal, 18 external) answered without errors.

Domain and trust

4 checks passed
  • Domain is 2 years old

    2 years

    hirschsecure.com was registered in Jun 2024 through Amazon Registrar, Inc.. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only letsencrypt.org, pki.goog, sectigo.com and globalsign.com to issue certificates for hirschsecure.com, so a mis-issued certificate from anyone else is refused.

  • DNSSEC is on

    hirschsecure.com's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.

  • Registered until Jun 2027

    hirschsecure.com is registered until Jun 2027.

Content and conversion

2 to fix86
  • 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.

  • Thin social proof

    Social proof on the homepage: “more than 12,000 customers”. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

  • About 545 words of copy

    The homepage carries about 545 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: “Get in Touch”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “Get in Touch” and “Contact Support”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • Risk reducer mentioned

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

Email authentication

100
  • Email authentication score: 100/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: reject

    DMARC tells receivers to reject mail that fails authentication, and sends you reports.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com include:_spf.salesforce.com ip4:54.174.209.165 ip4:54.189.247.173 ip4:52.100.…”.

  • DKIM signing found

    A DKIM key is published (selector “selector1” and “selector2”), so receivers can verify mail really came from you.

Privacy and tracking

  • 6 trackers load before any consent

    6

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

  • 10 cookies set on arrival

    10

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

  • 32 other companies contacted

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

1 checks passed
  • Consent tool: Usercentrics

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

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Vercel

Hiring

Hiring
3 open roles
Job board
workable

Company

Employees
130

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on hirschsecure.com, including 13 speed 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