7.2 sec in total
114 ms
6.2 sec
921 ms
Visit asafe.de now to see the best up-to-date A SAFE content and also check out these interesting facts you probably never knew about asafe.de
The world’s leading polymer industrial safety barrier and guardrail suitable for all industrial workplaces.
Visit asafe.deWe analyzed Asafe.de page load time and found that the first response time was 114 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
asafe.de performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value7.8 s
3/100
25%
Value7.6 s
25/100
10%
Value3,090 ms
2/100
30%
Value0
100/100
15%
Value12.0 s
16/100
10%
114 ms
320 ms
669 ms
27 ms
70 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Asafe.de, 67% (61 requests) were made to Webcdn.asafe.com and 8% (7 requests) were made to Asafe.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Webcdn.asafe.com.
Page size can be reduced by 149.2 kB (6%)
2.3 MB
2.2 MB
In fact, the total size of Asafe.de main page is 2.3 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. 70% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 94.0 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 94.0 kB or 80% of the original size.
Potential reduce by 47.2 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. A SAFE images are well optimized though.
Potential reduce by 3.3 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 4.6 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. Asafe.de needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 11% of the original size.
Number of requests can be reduced by 27 (33%)
82
55
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A SAFE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
asafe.de
114 ms
320 ms
669 ms
bootstrap.min.css
27 ms
core.css
70 ms
modernizr.min.js
38 ms
Get
116 ms
polyfill.min.js
401 ms
aspnet-validation.min.js
389 ms
email-decode.min.js
15 ms
api.js
41 ms
gtm.js
103 ms
products.css
436 ms
jquery.min.js
11 ms
content.bundle.js
538 ms
cookies.bundle.js
486 ms
tracking.bundle.js
721 ms
jquery.validate.min.js
15 ms
jquery.validate.unobtrusive.min.js
15 ms
api.js
30 ms
analytics.js
164 ms
globe-white.svg
494 ms
chevron-down-white-small.svg
150 ms
email.svg
530 ms
phone.svg
331 ms
asafe-logo-new.png
330 ms
search-icon-black.svg
599 ms
pillar-curve.png
335 ms
box-shadow-horizontal.png
450 ms
promat-web-banner.png
399 ms
reducing_operation_costs_protecting_people.jpg
401 ms
protecting_people_pedestrian_barrier.jpg
402 ms
safety_compliance_testing_area_with_cart.jpg
403 ms
smarter_safety_1156x556.jpg
405 ms
global_safety_standards_1156x556.jpg
450 ms
safety_innovation_1156x556.jpg
449 ms
virtual-asafe-homepage.jpg
1115 ms
pedestrian-barrier.jpg
927 ms
building-column-wall-protection.jpg
450 ms
rackend-barrier-protecting-rackend.jpg
454 ms
traffic-barrier-protecting-machinery.jpg
465 ms
dock-gate-protecting-dock-entrance.jpg
475 ms
microsoftteams-image.png
492 ms
pendulum-testing-tile-766-x-430-curve.jpg
1120 ms
placeholder.jpg
504 ms
polymer-barrier-protecting-machinery.jpg
1196 ms
traffic-barrier-protecting-metalwork.jpg
1316 ms
airport-safety-barriers.jpg
1292 ms
car-park-polymer-safety-barrier.jpg
1660 ms
polymer-barriers-protecting-new-building.jpg
1819 ms
bollards-protecting-machines.jpg
2027 ms
cold-storage-barrier.jpg
1913 ms
barrier-protecting-pedestrians-chemicals.jpg
1808 ms
295 ms
recaptcha__de.js
126 ms
Graphik-Medium.woff
1758 ms
Graphik-Regular.woff
1939 ms
collect
167 ms
fallback
190 ms
fallback
193 ms
Graphik-Light.woff
2045 ms
Graphik-ExtraLight.woff
2112 ms
iframeGate.bundle.js
2031 ms
collect
131 ms
food-and-drink.jpg
2304 ms
wall-barrier-protection-corridor.jpg
2030 ms
high-level-barrier-protecting-pedestrians-from-packaging.jpg
2451 ms
drone_sonoco_001.jpg
1952 ms
sonoco_logo_383_215.jpg
2469 ms
combilift_header_3000x1200.jpg
2618 ms
combiliftlogo.jpg
2543 ms
cc_northumberland_1_500x280.jpg
2693 ms
fallback__ltr.css
9 ms
cocacola_logo.jpg
2337 ms
qaweb03_766x430.jpg
3028 ms
site_survey.jpg
2909 ms
microsoftteams-image.png
3009 ms
quote.jpg
2996 ms
css
52 ms
ga-audiences
14 ms
a-safe_protection.jpg
3249 ms
facebook-icon.png
3057 ms
linkid.js
18 ms
tiktok-icon.png
3316 ms
linkedin-icon.png
3394 ms
collect
26 ms
pillar-curve.png
2966 ms
logo_48.png
18 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
48 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
60 ms
close.svg
3100 ms
asafe.de accessibility score
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
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.
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 IDs are not unique
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.
asafe.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
asafe.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Asafe.de 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 Asafe.de 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.
asafe.de
Open Graph data is detected on the main page of A SAFE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: