Website review, no card needed

nightowlsp.com logo

nightowlsp.com website review

Visit site (opens in a new tab)Reviewed 8 November 202638 issues · 82 checks

This review found 38 issues worth fixing on nightowlsp.com, 15 of them high impact, across 82 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
1.7 s1.4 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.5 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
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
174 ms142 msMay 16Oct 31155 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026154 ms
May 23, 2026153 ms
May 30, 2026150 ms
Jun 6, 2026146 ms
Jun 13, 2026146 ms
Jun 20, 2026148 ms
Jun 27, 2026150 ms
Jul 4, 2026153 ms
Jul 11, 2026153 ms
Jul 18, 2026153 ms
Jul 25, 2026150 ms
Aug 1, 2026150 ms
Aug 8, 2026150 ms
Aug 15, 2026152 ms
Aug 22, 2026156 ms
Aug 29, 2026162 ms
Sep 5, 2026163 ms
Sep 12, 2026167 ms
Sep 19, 2026170 ms
Sep 26, 2026169 ms
Oct 3, 2026170 ms
Oct 10, 2026163 ms
Oct 17, 2026161 ms
Oct 24, 2026158 ms
Oct 31, 2026155 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 nightowlsp.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nightowlsp.com at 0.8 s0.8 s
  2. nightowlsp.com at 1.6 s1.6 s
  3. nightowlsp.com at 2.4 s2.4 s
  4. nightowlsp.com at 3.1 s3.1 s
  5. nightowlsp.com at 3.9 s3.9 s
  6. nightowlsp.com at 4.7 s4.7 s
  7. nightowlsp.com at 5.5 s5.5 s
  8. nightowlsp.com at 6.3 s6.3 s

Speed

11 to fix49
  • Reduce unused JavaScript

    5.6 s · 1.0 MB

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

  • Mobile performance score: 49

    49/100

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

  • Main-thread work: 6.3 s

    A phone's processor spends 6.3 s on main-thread work while loading, 2.9 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 (Shopify, Wistia and Clarity and others), adding 2.3 MB and 1.5 s of main-thread time.

  • Minify JavaScript

    880 ms · 158 KiB

    158 KiB could be saved by minifying JavaScript.

  • Shopify adds 695 ms

    695 ms

    Shopify costs a phone 695 ms of main-thread work and 1.2 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.

  • Improve image delivery

    400 ms · 290 KiB

    15 images could be 290 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 75 KiB

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

  • Wistia adds 266 ms

    266 ms

    Wistia costs a phone 266 ms of main-thread work and 248 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.

  • 2,457 HTML elements

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

  • rebuyengine.com adds 122 ms

    122 ms

    rebuyengine.com costs a phone 122 ms of main-thread work and 297 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

    200 ms · 58 KiB

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

  • Reduce unused CSS

    210 ms · 29 KiB

    About 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 210 ms faster on a phone.

  • Render-blocking requests

    200 ms

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

  • 16 long tasks on the main thread

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

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

  • Duplicated JavaScript

    5 KiB

    5 KiB JavaScript is shipped twice across bundles.

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

    9 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 22.9 s

    22.9 s

    Your largest element takes 22.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 24.0 s

    24.0 s

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

  • Speed Index: 11.7 s

    11.7 s

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

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user INP: 202 ms

    202 ms

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

  • Total Blocking Time: 331 ms

    331 ms

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

4 checks passed
  • 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.4 s

    1.4 s

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

  • Real-user TTFB: 712 ms

    712 ms

    Real visitors wait 712 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

1 to fix70
  • Page weight: 4.6 MB in 390 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 390 requests on a phone: scripts 2.6 MB (180), images 922 KiB (39) and other files 782 KiB (118). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.32 g

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

6 to fixGoogle 9392
  • 51 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 16 images without alt text

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

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

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

  • 1 link without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 9288
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “We clean up after ourselves.”). One clear main headline is easier for people and search engines.

  • Meta description is long (200 characters)

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

  • 2 links with vague text

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

  • 100 internal links, 20 external

    The homepage links to 100 pages on nightowlsp.com and 20 external pages.

6 checks passed
  • Title: 59 characters

    Your title is a healthy 59 characters: “Night Owl Security Products - Home Page – Night Owl SP, LLC”.

  • Canonical URL set

    The canonical URL is https://nightowlsp.com/.

  • Structured data in place

    Structured data found: Organization and 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://nightowlsp.com/sitemap.xml.

AI search readiness

100
4 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.

  • 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 (1,550 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://nightowlsp.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://nightowlsp.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://nightowlsp.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://nightowlsp.com/collections/all, https://nightowlsp.com/customer_authentication/redirect and https://nightowlsp.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://nightowlsp.com/customer_authentication/redirect has 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 47 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    6 pages of 15 loaded without an error (the rest turned automated requests away).

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

Best practices

1 to fixGoogle 9693
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Unexpected number”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 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 945 words of copy

    The homepage carries about 945 words of visible text.

2 checks passed
  • 15 calls to action

    The homepage has 15 calls to action, for example “What Should I Buy?”, “Learn More” and “Shop Now”.

  • 14 short forms

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

Privacy and tracking

  • 2 trackers load before any consent

    2

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

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 2 of them by other companies (measured from a US location before any click).

  • 33 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) 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 nightowlsp.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus;Syndigo
Hosting
Shopify

Company

Headquarters
Harrodsburg

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on nightowlsp.com, including 19 speed issues, 3 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