4.7 sec in total
204 ms
4.1 sec
420 ms
Welcome to 2n.cz homepage info - get ready to check 2N best content for Egypt right away, or after learning these important things about 2n.cz
2N is a European company that manufacture and develop door access control systems which include IP intercoms, answering units and other security devices and software. Its market-leading portfolio of p...
Visit 2n.czWe analyzed 2n.cz page load time and found that the first response time was 204 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
2n.cz performance score
name
value
score
weighting
Value5.3 s
8/100
10%
Value12.8 s
0/100
25%
Value10.2 s
8/100
10%
Value4,340 ms
1/100
30%
Value0.113
86/100
15%
Value29.2 s
0/100
10%
204 ms
399 ms
208 ms
73 ms
125 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 2n.cz, 80% (107 requests) were made to 2n.com and 12% (16 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source 2n.com.
Page size can be reduced by 426.2 kB (11%)
3.7 MB
3.3 MB
In fact, the total size of 2n.cz main page is 3.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. 85% 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 3.0 MB which makes up the majority of the site volume.
Potential reduce by 158.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 158.0 kB or 81% of the original size.
Potential reduce by 92.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. 2N images are well optimized though.
Potential reduce by 41.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 41.0 kB or 14% of the original size.
Potential reduce by 134.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. 2n.cz needs all CSS files to be minified and compressed as it can save up to 134.5 kB or 49% of the original size.
Number of requests can be reduced by 51 (49%)
104
53
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2N. 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 9 to 1 for CSS and as a result speed up the page load time.
2n.cz
204 ms
www.2n.com
399 ms
208 ms
gtm.js
73 ms
jquery.js
125 ms
jquery-migrate-1.2.1.min.js
33 ms
qazy.min.js
213 ms
design.min.js
488 ms
2n-theme.min.js
483 ms
bootstrap-transition.js
483 ms
bootstrap-collapse.js
485 ms
aui.css
486 ms
main.css
484 ms
main.css
505 ms
main.css
505 ms
main.css
506 ms
main.css
507 ms
main.css
516 ms
barebone.jsp
810 ms
main.js
517 ms
main.js
517 ms
main.js
518 ms
navigation.js
517 ms
main.css
795 ms
js
59 ms
js
56 ms
js
57 ms
js
63 ms
js
60 ms
js
117 ms
main.js
610 ms
main.js
599 ms
jquery.easing.1.3.min.js
611 ms
slick.min.js
610 ms
controls.min.js
696 ms
28713090.js
594 ms
landing
96 ms
js
89 ms
destination
86 ms
destination
50 ms
js
196 ms
js
198 ms
js
263 ms
js
193 ms
js
257 ms
js
190 ms
90846ba9-105b-47e8-b566-c063e6c263bb
257 ms
5fcc0665-72bc-4253-9f9c-62087515f83f
339 ms
04c1c5b1-a961-492d-8a36-f7d3599e1ed5
256 ms
f237f011-a573-46bd-8ffb-f51a41b0caff
340 ms
ae34c18d-58ef-4d54-92d6-53865c493f03
338 ms
ffe729c2-9c36-49d1-a754-48020888ee61
255 ms
07e9accf-0fc3-46f5-9852-56e5ed288349
341 ms
6928c193-257e-49a7-bb0e-3c496a23fdf4
340 ms
e11a9e6b-7c9b-4b00-8dc6-3f2289730915
342 ms
c6d05cd1-9bc5-4e5e-8dfa-ef22a63b1074
415 ms
3ec70c63-951f-48f4-9826-d5bb08a8b27b
413 ms
d021111d-4589-4d9c-935b-303cd7f5c899
414 ms
31a81b1e-68a1-4362-8f60-03bdc023d881
415 ms
1b487a39-d945-4686-93a2-fa3f125c930c
415 ms
3bce457a-52a8-4037-b887-a2e493554b92
415 ms
3f674e7f-dcc5-4001-b356-0fcac9242676
483 ms
ff783723-a5ff-4ea5-8351-14cb51e8dff6
485 ms
6dbbf045-3dfe-4197-bc25-346b37d13821
486 ms
c86c3bc9-05ab-4422-80e1-d68e2d434364
489 ms
09dab018-a7da-4c14-8021-42cf60ace28a
490 ms
bat.js
333 ms
javascript.heeet.io
478 ms
api.min.js
333 ms
LOGO_WEB.svg
243 ms
412e32b0-9bf4-4f47-8078-8edf0abdbd87
458 ms
ef5d87fa-3524-4114-b156-ce27dc1d62db
306 ms
c4a50ca0-f064-482f-a51c-a0ff8f11a0d9
1662 ms
2446cc54-b199-4ba4-a12c-d24a426de8d7
532 ms
Where.png
457 ms
Contact.png
458 ms
Newsletter.png
459 ms
6ad36b5d-55e6-4339-9e38-b779ae6a4bce
511 ms
5d30c13a-51ee-48fa-b412-5c87248fbb98
459 ms
051c6723-02bc-4eba-bac7-86f327ea820d
459 ms
93c4cf60-5ee1-4435-aa17-7c9317587152
508 ms
GothamSSm-Light.otf
1493 ms
GothamSSm-ExtraLight.otf
1498 ms
GothamSSm-Medium.otf
1492 ms
GothamSSm-Bold.otf
1496 ms
e3657b37-af51-4ce5-81c7-e32282cd7887
1433 ms
89b99702-e6a6-48fa-9921-37a4022c13ac
1433 ms
c063fb45-dd6f-42ea-8c41-b4a79e1b6b6d
1434 ms
fc2afff7-a197-4913-a429-a3f581589efc
1437 ms
5fcc0665-72bc-4253-9f9c-62087515f83f
1438 ms
04c1c5b1-a961-492d-8a36-f7d3599e1ed5
1438 ms
f237f011-a573-46bd-8ffb-f51a41b0caff
1439 ms
1bc8e1e3-b8fb-45ad-a10c-adb4cf7749b7
1366 ms
15448024-6caa-41d0-9aae-d43d2f5d5fd7
1371 ms
ecd211a3-2217-41df-b640-00dd7f726cae
1388 ms
a7d4bdd7-b6e1-4476-b03c-6aa3cc28404c
1367 ms
305da508-9026-4dde-9879-20d1603a6da5
1374 ms
4c710615-cdbb-47c3-9c88-48e5b452951b
1366 ms
87652a8d-9456-45ad-99f3-0b9a408d17e8
1367 ms
d5a1a00b-80a1-4ea3-9bfc-890d04c6a983
1367 ms
97058990.js
26 ms
fontawesome-webfont.woff
1213 ms
e11a9e6b-7c9b-4b00-8dc6-3f2289730915
1195 ms
c6d05cd1-9bc5-4e5e-8dfa-ef22a63b1074
1195 ms
3ec70c63-951f-48f4-9826-d5bb08a8b27b
1196 ms
d021111d-4589-4d9c-935b-303cd7f5c899
1196 ms
31a81b1e-68a1-4362-8f60-03bdc023d881
1197 ms
97058990
1164 ms
052740fe-8ab6-48af-8a4c-9cb882cc377d
1175 ms
17ac5059-accd-45ff-9413-dbf2d7f97ef6
1173 ms
510c1560-2432-49c8-94bd-e5057f70ffec
1175 ms
e0157608-dd86-45a2-b5ea-39b943c9cf35
1175 ms
1009a012-025a-4882-9af0-fd45e7cb7f1b
1176 ms
37a04073-bb3d-4975-adac-adf538230754
1176 ms
2cc1fb35-ae2b-46ea-9041-069d3d514d25
1176 ms
1134 ms
ffe729c2-9c36-49d1-a754-48020888ee61
1117 ms
07e9accf-0fc3-46f5-9852-56e5ed288349
1119 ms
6928c193-257e-49a7-bb0e-3c496a23fdf4
184 ms
3bce457a-52a8-4037-b887-a2e493554b92
185 ms
3f674e7f-dcc5-4001-b356-0fcac9242676
187 ms
ff783723-a5ff-4ea5-8351-14cb51e8dff6
187 ms
6dbbf045-3dfe-4197-bc25-346b37d13821
188 ms
c86c3bc9-05ab-4422-80e1-d68e2d434364
187 ms
09dab018-a7da-4c14-8021-42cf60ace28a
210 ms
1bc8e1e3-b8fb-45ad-a10c-adb4cf7749b7
211 ms
89817434-6256-456f-bb77-76489b05bb14
288 ms
clarity.js
20 ms
99 ms
052740fe-8ab6-48af-8a4c-9cb882cc377d
104 ms
98 ms
available_languages.jsp
104 ms
104 ms
2n.cz 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.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
2n.cz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
2n.cz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Document doesn't have a valid hreflang
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 2n.cz 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 2n.cz 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.
2n.cz
Open Graph data is detected on the main page of 2N. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: