Website review, no card needed
deltascientific.com website review
Visit site (opens in a new tab)Reviewed 21 November 202634 issues · 83 checks
This review found 34 issues worth fixing on deltascientific.com, 13 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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
Site score
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 5.1 s |
| Jun 6, 2026 | 5.1 s |
| Jun 13, 2026 | 5.0 s |
| Jun 20, 2026 | 5.1 s |
| Jun 27, 2026 | 5.1 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 5.0 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 4.9 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.9 s |
| Oct 10, 2026 | 5.3 s |
| Oct 17, 2026 | 5.3 s |
| Oct 24, 2026 | 5.6 s |
| Oct 31, 2026 | 5.9 s |
| Nov 7, 2026 | 5.9 s |
| Nov 14, 2026 | 6.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 90 ms |
| Jun 6, 2026 | 91 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 100 ms |
| Jul 18, 2026 | 101 ms |
| Jul 25, 2026 | 101 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 97 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 94 ms |
| Aug 29, 2026 | 91 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 97 ms |
| Sep 19, 2026 | 107 ms |
| Sep 26, 2026 | 103 ms |
| Oct 3, 2026 | 103 ms |
| Oct 10, 2026 | 108 ms |
| Oct 17, 2026 | 109 ms |
| Oct 24, 2026 | 137 ms |
| Oct 31, 2026 | 154 ms |
| Nov 7, 2026 | 164 ms |
| Nov 14, 2026 | 166 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
How it loaded on a phone
0.6 s
1.1 s
1.7 s
2.3 s
2.9 s
3.4 s
4.0 s
4.6 s
Speed
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: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,259 HTML elements
The page has 4,259 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cookiebot and Clarity and others), adding 811 KiB and 1.6 s of main-thread time.
Google Tag Manager adds 892 ms
892 msGoogle Tag Manager costs a phone 892 ms of main-thread work and 521 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.
Use efficient cache lifetimes
500 ms · 49 KiB5 files are served with short cache lifetimes, so returning visitors download them again (49 KiB).
Cookiebot adds 521 ms
521 msCookiebot costs a phone 521 ms of main-thread work and 166 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.
Improve image delivery
441 KiB4 images could be 441 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 429 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 87 KiBAbout 87 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.
Reduce unused JavaScript
319 KiBAbout 319 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 129 ms
129 msYour server sent the HTML in 129 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 LCP: 5.5 s
5.5 sReal visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.1 s
5.1 sReal visitors see the first content after 5.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.2 s
4.2 sReal visitors wait 4.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 7.7 s
7.7 sYour largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “VEHICLE BARRICADE & PERIMETER SECURITY SYSTEMS MP5000: STOP…”.
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 82% slower for real visitors
+82%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 90 ms to 166 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 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.
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.1 s to 6.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.064
0.064The layout barely moves while loading (CLS 0.064, good is under 0.1).
Images and page weight
Page weight: 3.0 MB in 191 requests
3.0 MBYour homepage downloads 3.0 MB in 191 requests on a phone: scripts 1.5 MB (111), images 1.1 MB (14) and stylesheets 154 KiB (36). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 102.0 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
45 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: 45 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
13 links with vague text
13 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
129 internal links, 9 external
The homepage links to 129 pages on deltascientific.com and 9 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Vehicle barricade systems with high security bollards, anti ram & crash rated barriers for vehicle access control used …”.
One H1 headline
Your main headline reads: “Vehicle Barricade & Perimeter Security Systems”.
Title: 58 characters
Your title is a healthy 58 characters: “High Security Vehicle Barricade Systems | Delta Scientific”.
Canonical URL set
The canonical URL is https://deltascientific.com/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and 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://deltascientific.com/sitemap_index.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 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 (2,811 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://deltascientific.com/llms.txt (14 KiB, 41 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://deltascientific.com/product/anti-climb-pedestrian-door-j10037, whose canonical is https://deltascientific.com/product/anti-climb-gate-j10037. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages slow to respond
https://deltascientific.com/our-history, https://deltascientific.com/quick-facts, https://deltascientific.com/lunch-and-learn, https://deltascientific.com/delta-scientific-patents, https://deltascientific.com/high-security-barricades and https://deltascientific.com/high-security-barricades/wedge-barricades and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
6 small tap targets
6 of 17 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 “wp is not defined”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 9 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
A 25-field form
Your longest form asks for 25 fields (12 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 764 words of copy
The homepage carries about 764 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: “Quote (0)” and “Learn More”.
23 calls to action
The homepage has 23 calls to action, for example “Quote (0)”, “Contact” and “Join Our Newsletter”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 1 of them by other companies (measured from a US location before any click).
23 other companies contacted
Loading the homepage contacts 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 deltascientific.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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- WordPress.com
Company
- Founded
- 1974
- Headquarters
- Palmdale
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on deltascientific.com, including 23 speed issues, 1 SEO issue 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.