Website review, no card needed
edgeworthsecurity.com website review
Visit site (opens in a new tab)Reviewed 24 October 202627 issues · 76 checks
This review found 27 issues worth fixing on edgeworthsecurity.com, 7 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.5 s
Speed
Reduce unused JavaScript
1.8 s · 849 KiBAbout 849 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.1 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 68
68/100Your mobile performance score is 68 (desktop: 87). Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Squarespace, Google CDN and Other Google APIs/SDKs and others), adding 2.5 MB and 657 ms of main-thread time.
Reduce unused CSS
600 ms · 165 KiBAbout 165 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Squarespace adds 381 ms
381 msSquarespace costs a phone 381 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.
Google CDN adds 240 ms
240 msGoogle CDN costs a phone 240 ms of main-thread work and 741 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.
squarespace-cdn.com adds 1 ms
1 mssquarespace-cdn.com costs a phone 1 ms of main-thread work and 441 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
150 ms · 93 KiBPolyfills for old browsers add 93 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
132 KiB4 images could be 132 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 128 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
8 KiB3 files are served with short cache lifetimes, so returning visitors download them again (8 KiB).
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.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 769 ms of it running JavaScript. That is comfortably low.
Server response: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.5 s
8.5 sYour largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 16.7 s
16.7 sThe page becomes fully interactive after 16.7 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 109 ms
109 msScripts block the page for only 109 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.022
0.022The layout barely moves while loading (CLS 0.022, good is under 0.1).
Images and page weight
Page weight: 2.9 MB in 89 requests
2.9 MBYour homepage downloads 2.9 MB in 89 requests on a phone: scripts 1.8 MB (55), images 381 KiB (11) and other files 353 KiB (5). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
GOLD+SECTION+02.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.8 g of CO₂ per visit
0.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.5 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
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
47 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: 47 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/68483b5b27f3bc299c5…”.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
43 internal links, 2 external
The homepage links to 43 pages on edgeworthsecurity.com and 2 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Edgeworth provides advanced physical and digital security solutions using AI and analytics, ensuring safety, protection…”.
One H1 headline
Your main headline reads: “our suite of solutions”.
Title: 34 characters
Your title is a healthy 34 characters: “Edgeworth | Enhance Security Today”.
Canonical URL set
The canonical URL is https://www.edgeworthsecurity.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.edgeworthsecurity.com/sitemap.xml.
AI search readiness
Organization data is thin (0 of 6 facts)
Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.edgeworthsecurity.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.
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 (315 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a title
https://www.edgeworthsecurity.com/privacy-policy, https://www.edgeworthsecurity.com/terms-of-use and https://www.edgeworthsecurity.com/trademark-notice all use the title “Terms of Service 1 — Edgeworth”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://www.edgeworthsecurity.com/privacy-policy, https://www.edgeworthsecurity.com/terms-of-use and https://www.edgeworthsecurity.com/trademark-notice have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://www.edgeworthsecurity.com/remote-guard, https://www.edgeworthsecurity.com/intelligence, https://www.edgeworthsecurity.com/network-operations, https://www.edgeworthsecurity.com/integration, https://www.edgeworthsecurity.com/executive-protection and https://www.edgeworthsecurity.com/global-services and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.edgeworthsecurity.com/contact 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.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/68483b5b27f3bc299c5bb4ba/74/5c5a…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
8 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 286 words of copy
The homepage carries about 286 words of visible text.
4 checks passed
9 calls to action
The homepage has 9 calls to action, for example “CONTACT US”, “LEARN MORE” and “Contact”.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 edgeworthsecurity.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
- Squarespace
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on edgeworthsecurity.com, including 13 speed issues, 2 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.