14.1 sec in total
2.5 sec
11 sec
521 ms
Click here to check amazing CEO SAFETY content. Otherwise, check out these important facts you probably never knew about ceosafety.ng
C.E.O SECURITY SYSTEMS LTDThe Best choice in a Electronic security and Safety businessSHOP NOWC.E.O SECURITY SYSTEMS LTDThe Best choice in a Electronic security and Safety businessSHOP NOWC.E.O SECURI...
Visit ceosafety.ngWe analyzed Ceosafety.ng page load time and found that the first response time was 2.5 sec and then it took 11.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ceosafety.ng performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value15.8 s
0/100
25%
Value20.9 s
0/100
10%
Value11,460 ms
0/100
30%
Value0.017
100/100
15%
Value24.6 s
0/100
10%
2549 ms
142 ms
262 ms
279 ms
337 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 79% of them (110 requests) were addressed to the original Ceosafety.ng, 19% (27 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Ceosafety.ng.
Page size can be reduced by 240.3 kB (9%)
2.7 MB
2.4 MB
In fact, the total size of Ceosafety.ng main page is 2.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 207.7 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 29.7 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 207.7 kB or 87% of the original size.
Potential reduce by 15.6 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. CEO SAFETY images are well optimized though.
Potential reduce by 2.4 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Potential reduce by 14.5 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Ceosafety.ng has all CSS files already compressed.
Number of requests can be reduced by 80 (74%)
108
28
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CEO SAFETY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
ceosafety.ng
2549 ms
wp-emoji-release.min.js
142 ms
style.min.css
262 ms
wc-blocks-vendors-style.css
279 ms
wc-blocks-style.css
337 ms
style-index.css
379 ms
styles.css
233 ms
woocommerce-layout.css
273 ms
woocommerce.css
347 ms
wp-ulike.min.css
449 ms
font-awesome.min.css
386 ms
simple-line-icons.css
415 ms
htflexboxgrid.css
416 ms
slick.css
436 ms
woolentor-widgets.css
486 ms
base.css
655 ms
auxin-icon.css
572 ms
main.css
725 ms
elementor-icons.min.css
652 ms
frontend-legacy.min.css
459 ms
frontend.min.css
608 ms
post-72.css
722 ms
elementor.css
866 ms
elementor-widgets.css
1145 ms
mediaelementplayer-legacy.min.css
857 ms
wp-mediaelement.min.css
859 ms
frontend.min.css
996 ms
post-108.css
860 ms
css
61 ms
custom.css
978 ms
post-147.css
968 ms
post-198.css
991 ms
css
85 ms
jquery.min.js
960 ms
jquery-migrate.min.js
1059 ms
modernizr-custom.min.js
1374 ms
font-awesome.min.css
1067 ms
fontawesome.min.css
1033 ms
brands.min.css
1071 ms
regular.min.css
977 ms
solid.min.css
1063 ms
animations.min.css
1075 ms
imagesloaded.min.js
1896 ms
masonry.min.js
1009 ms
plugins.min.js
1832 ms
widgets.js
1787 ms
mediaelement-and-player.min.js
1439 ms
mediaelement-migrate.min.js
1430 ms
wp-mediaelement.min.js
1744 ms
script.js
1742 ms
plugins.min.js
1841 ms
scripts.js
1828 ms
regenerator-runtime.min.js
1989 ms
wp-polyfill.min.js
1722 ms
index.js
1788 ms
jquery.blockUI.min.js
1789 ms
add-to-cart.min.js
1790 ms
js.cookie.min.js
1772 ms
woocommerce.min.js
1642 ms
cart-fragments.min.js
1852 ms
wp-ulike.min.js
1849 ms
slick.min.js
1852 ms
accordion.min.js
1780 ms
scripts.min.js
1833 ms
custom.js
1673 ms
jquery.countdown.min.js
1777 ms
underscore.min.js
1780 ms
wp-util.min.js
1827 ms
add-to-cart-variation.min.js
1771 ms
woolentor-widgets-active.js
1759 ms
forms.js
1922 ms
webpack.runtime.min.js
1867 ms
frontend-modules.min.js
1855 ms
jquery.sticky.min.js
1925 ms
frontend.min.js
1989 ms
waypoints.min.js
1783 ms
core.min.js
1795 ms
swiper.min.js
1806 ms
share-link.min.js
1330 ms
dialog.min.js
1353 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
284 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
347 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
344 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
345 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
349 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
347 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
348 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
351 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
349 ms
frontend.min.js
1383 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
350 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
350 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
350 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
350 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
351 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
353 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
350 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
353 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
352 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf
315 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf
319 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0ow.ttf
319 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXh0ow.ttf
316 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXh0ow.ttf
318 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0ow.ttf
319 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf
319 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0ow.ttf
319 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXh0ow.ttf
319 ms
preloaded-modules.min.js
1063 ms
auxin-front.woff
1329 ms
eicons.woff
1269 ms
Simple-Line-Icons.ttf
1264 ms
cropped-LOGO-2-1.png
1323 ms
downarrow.svg
1147 ms
empty-cart.svg
1148 ms
WhatsApp-Image-2022-05-27-at-1.31.36-PM.jpeg
1384 ms
WhatsApp-Image-2022-05-27-at-1.31.39-PM.jpeg
1163 ms
WhatsApp-Image-2022-05-27-at-1.31.42-PM.jpeg
1198 ms
WhatsApp-Image-2022-05-27-at-1.31.35-PM.jpeg
1247 ms
Landing-Valve-1.png
1188 ms
Fingerprint-office-lock-1-768x768.png
1196 ms
WiFi-remote-covert-camera-2.png
1329 ms
Garrett-hand-held-metal-detector.png
1207 ms
No-Touch-Exit-Button-with-remote-1.png
1314 ms
ZKT-Iface-702-Time-and-Attendance-Machine.png
1285 ms
2mp-camera-300x300.jpg
1107 ms
f19-300x300.jpg
1113 ms
smoke-2-300x300.webp
1219 ms
Face-Recognition-Lock-D1306-300x300.jpg
1214 ms
smoke-300x300.jpg
1165 ms
PIR-300x300.jpg
1190 ms
Landing-Valve-300x276.png
1318 ms
5-in-one-2.jpg
1204 ms
extinguisher-300x300.png
1278 ms
800-type-300x300.jpg
1147 ms
ceosafety.ng
1852 ms
symbols.svg
801 ms
admin-ajax.php
838 ms
woocommerce-smallscreen.css
114 ms
ceosafety.ng accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ceosafety.ng best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ceosafety.ng SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ceosafety.ng can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ceosafety.ng main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
ceosafety.ng
Open Graph data is detected on the main page of CEO SAFETY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: