11.3 sec in total
1.9 sec
8.4 sec
970 ms
Welcome to cms.national-geographic.pl homepage info - get ready to check Cms National Geographic best content for Poland right away, or after learning these important things about cms.national-geographic.pl
Odwiedź National Geographic Polska - światowego lidera w dziedzinie nauki i eksploracji. Razem z nami odkrywaj historię, ludzi, przyrodę, zgłębiaj naukę o świecie i kosmosie.
Visit cms.national-geographic.plWe analyzed Cms.national-geographic.pl page load time and found that the first response time was 1.9 sec and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
cms.national-geographic.pl performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value11.4 s
0/100
25%
Value9.0 s
14/100
10%
Value3,390 ms
2/100
30%
Value0.219
57/100
15%
Value23.2 s
1/100
10%
1856 ms
1286 ms
12 ms
348 ms
37 ms
Our browser made a total of 221 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Cms.national-geographic.pl, 23% (51 requests) were made to National-geographic.pl and 8% (17 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source National-geographic.pl.
Page size can be reduced by 754.1 kB (18%)
4.2 MB
3.4 MB
In fact, the total size of Cms.national-geographic.pl main page is 4.2 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. 75% 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.3 MB which makes up the majority of the site volume.
Potential reduce by 79.1 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 79.1 kB or 78% of the original size.
Potential reduce by 220.5 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. Cms National Geographic images are well optimized though.
Potential reduce by 248.8 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 248.8 kB or 52% of the original size.
Potential reduce by 205.8 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. Cms.national-geographic.pl needs all CSS files to be minified and compressed as it can save up to 205.8 kB or 82% of the original size.
Number of requests can be reduced by 94 (46%)
203
109
The browser has sent 203 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cms National Geographic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
cms.national-geographic.pl
1856 ms
www.national-geographic.pl
1286 ms
font-awesome.min.css
12 ms
c218f74.css
348 ms
jquery.min.js
37 ms
jquery.cookiebar.js
234 ms
b666ee8.css
235 ms
gemius.js
325 ms
ado.js
422 ms
788b911.js
391 ms
video-js.css
42 ms
baabf01.css
124 ms
video.js
63 ms
f8a9012.js
285 ms
fpdata.js
127 ms
xgemius.js
534 ms
logo.png
133 ms
8422
455 ms
a8ad351e219c1b27007da03b6ccfe8b2ddf02a56.jpg
129 ms
0614ab900c4f733afe92e4127099ccb1b54b62ab.png
2104 ms
a552598d100c7e290bf9c3797b284630d0d97400.jpeg
488 ms
5cd6034af537694c5c59913cb8adc40a959088a9.jpeg
487 ms
98ffd213bb7afc54e8cd4e6cf5c2cdc6a860ac89.jpeg
363 ms
cf1d67d7aa1fb20b96979f8bd6bb61a8649bb38e.jpeg
461 ms
751f5fde9bde8e5e5b71f3b467485de1f816c806.png
506 ms
8a90b84a4aa109444a56aeff0ccb9b81853770d0.jpeg
506 ms
a552598d100c7e290bf9c3797b284630d0d97400.jpeg
576 ms
0cba04a4d54dd70afa802435a627616029b1a991.jpeg
603 ms
ea206e5d6bd95dd8326188f5710f5bbe1f899bcb.jpeg
602 ms
12513eba5789ad96b972d2279d15ea531b56d774.jpeg
623 ms
d8ea9ae55f43420e02447d60ca5b6031710efcb1.jpeg
624 ms
40f9b2206e632354efb94a79f1650844412c28e7.jpeg
690 ms
04287dfbf618fa9fbce55e6eaa10358915438be4.jpeg
712 ms
e0b6f7503f39272cfc9bd75308650c7e2ad447c2.jpeg
721 ms
8bd57c6645c3b463b7fc1db39acffe00d280fc46.jpeg
739 ms
b3201f681894e11e880816e0de25fa6b1c0aa18f.jpeg
740 ms
a932c31ae0389b64356a542b42e5508aa2cef3a7.jpeg
804 ms
b1cdb49b8563187d5820be2370a802511042fc1f.jpeg
827 ms
6ffaee6c8878bb8b76621c39e355a8e73a055c66.jpeg
837 ms
20ab74ae97b1f0758ed5f12a5147a7e66092867e.jpeg
856 ms
367d5d35c38aec4ad264989396bc5d5fce290bb5.jpeg
859 ms
46f6ab87a4c7572dbf8ef45fbceec58ed6238837.jpeg
919 ms
80d64b7533080d83325fd00d66a9568388a6c558.png
1286 ms
dd79aff36102b80746380a11291d0d5c086747e3.jpeg
1749 ms
24b40ac3a4c1381ab0e19cc1eb42775b44ad1a6f.jpeg
974 ms
56963061abe04393771f986405ed03ebe382df17.jpeg
975 ms
344b9c54f20bd3cb468cbeb3b5426e1622b3010e.jpeg
1032 ms
4054ab74a9164348d9b0b3bc53876c44d9290a35.jpeg
1326 ms
ff603ee75dce14b1c887fc3c9cf66bb60948624e.jpeg
1327 ms
79a56a337cf5e863b17491a163988d472cb4b238.jpg
1147 ms
android.png
1261 ms
apple.png
1376 ms
subscription.png
1399 ms
gtm.js
60 ms
gTHiwyxi6S7iiHpqAoiE3Ba1RVmPjeKy21_GQJaLlJI.woff
58 ms
fontawesome-webfont.woff
16 ms
lsget.html
256 ms
17 ms
f288e289784e236f4db2e8ad8c7d5e518b32fe20.jpg
1320 ms
bootstrap2.min.css
11 ms
7268c440403a2bc8d9e8a73378f45ed32015e2f1.jpeg
1316 ms
ga.js
69 ms
1724866_465549030301772_354886357_n.jpg
91 ms
1515284_1691296941158381_1351520704_n.jpg
87 ms
10818101_515138108657026_824651906_n.jpg
88 ms
12825792_1160327244011589_1884004552_n.jpg
87 ms
10632221_174845836233030_1765098207_n.jpg
114 ms
12530833_881702091975876_1568108553_n.jpg
115 ms
11325977_970361426380303_848947113_n.jpg
115 ms
915588_615654015255078_95734117_n.jpg
116 ms
12825829_125944597799061_570313774_n.jpg
114 ms
all.js
110 ms
pl1-sst-w.js
84 ms
analytics.js
53 ms
__utm.gif
35 ms
sm.js
355 ms
ad.xml
110 ms
collect
19 ms
suiapi.js
69 ms
collect
93 ms
49 ms
xd_arbiter.php
67 ms
xd_arbiter.php
141 ms
sui.html
9 ms
loginbox
1218 ms
prenumerata-sidebar.jpg
1060 ms
redot.js
109 ms
photo-inner2.png
1080 ms
black-bg.png
1080 ms
icon-ng-list.png
1129 ms
events-icon.png
1176 ms
redot.js
106 ms
r.gif
236 ms
xd_arbiter.php
38 ms
page.php
114 ms
ad.js
106 ms
page.php
119 ms
handshake.js
493 ms
BWiYMciaraP.css
88 ms
Hy2B8ciSPhU.css
110 ms
q68gy-v_YMF.js
160 ms
oOzoJ_WOIGQ.js
189 ms
ihptErjAmMX.js
188 ms
1BQnIVjTFoC.js
202 ms
juKryPYAUFc.js
213 ms
cUsKAwzqrQw.js
222 ms
sarg=56EAEB06E56285B7
432 ms
ad.js
421 ms
12801356_10153995714494700_2772408530933051993_n.png
274 ms
wL6VQj7Ab77.png
76 ms
s7jcwEQH7Sx.png
75 ms
6GqoI2ZyIrf.png
74 ms
12049494_10153995688969700_5293400379126922006_n.png
124 ms
12832365_127791170948218_6737050107342149261_n.jpg
167 ms
12814685_133682560357859_1069217501526429748_n.jpg
126 ms
11828649_1656711467878133_7880643500602345785_n.jpg
174 ms
546971_285627328224284_658696964_n.jpg
168 ms
1379841_10150004552801901_469209496895221757_n.jpg
125 ms
12359936_758746817591912_4397571204346037603_n.jpg
125 ms
12644680_1181790128512705_6802204116912127822_n.jpg
273 ms
12669542_1272941042722194_1900102503794379461_n.jpg
141 ms
943950_1283405398342425_2550077613574108101_n.png
138 ms
12208386_855898291196166_1127347831946748588_n.jpg
179 ms
12250032_1647065655570907_8121204243834029309_n.jpg
158 ms
12439545_896552950443495_1909574021307900476_n.jpg
298 ms
1480518_881683558518727_8952196528316593260_n.jpg
191 ms
10383119_1381160905510021_1729675777217831501_n.jpg
182 ms
12074733_1635832330002604_4501073413295640283_n.jpg
253 ms
sarg=56EAEB06E56285B7
110 ms
billboard_gao_lib.js
106 ms
bgimage_gao_lib.js
106 ms
sarg=56EAEB06E56285B7
157 ms
R9a_DtVRZgv.js
22 ms
cUDgRFxaoIk.js
33 ms
0JBr1QHp8Gi.js
26 ms
kDOzhTr2W91.js
30 ms
NG-sensodyne-1366x768.jpg
248 ms
adServer.bs
81 ms
show_ads.js
7 ms
Focus-sensodyne.png
805 ms
ca-pub-5512390705137507.js
69 ms
sarg=56EAEB06E56285B7
231 ms
adsbygoogle.js
9 ms
zrt_lookup.html
123 ms
show_ads_impl.js
51 ms
sarg=56EAEB06E56285B7
209 ms
sarg=56EAEB06E56285B7
201 ms
ads
207 ms
osd.js
25 ms
ads
182 ms
sarg=56EAEB06E56285B7
181 ms
ads
157 ms
sarg=56EAEB06E56285B7
147 ms
9198.js
20 ms
ads
208 ms
sync
17 ms
346644-15.js
151 ms
336x280_srodtekst_R2.html
347 ms
300x250_R2.html
389 ms
300x600_R2.html
360 ms
ads.js
42 ms
300x250_BTF_R2.html
318 ms
bounce
17 ms
sarg=56EAEB06E56285B7
110 ms
ddc.htm
17 ms
emily.html
25 ms
emily.html
20 ms
sarg=56EAEB06E56285B7
107 ms
sarg=56EAEB06E56285B7
112 ms
tap.php
4 ms
tap.php
6 ms
ads
196 ms
ads
205 ms
ads
186 ms
ads
236 ms
2530
51 ms
push
50 ms
300x250_R3.html
111 ms
300x600_R3.html
136 ms
612413816e3ea048005f9acaa1ee5cda_1.html
187 ms
m
38 ms
pixel
13 ms
300x250_BTF_R3.html
107 ms
ads
251 ms
ads
204 ms
ads
243 ms
st.v2.js
132 ms
91208106c809ac740aa1511ccab00e6f.jpg
146 ms
cvo.gif
35 ms
15278422706574467143
81 ms
abg.js
81 ms
m_js_controller.js
94 ms
googlelogo_color_112x36dp.png
129 ms
css
112 ms
js
143 ms
s
37 ms
x_button_blue2.png
38 ms
push
60 ms
gr
40 ms
imgad
41 ms
nessie_icon_thin_arrow_big_white.png
19 ms
pixel_details.html
68 ms
cse
291 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
4 ms
img
64 ms
pixel
22 ms
push
60 ms
ck-confirm
43 ms
activeview
14 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
98 ms
Q116_Wu_Com_AwarenessM_V4_D_300x250_EN_US.jpg
48 ms
lidar.js
20 ms
sbhK2lTE.js
29 ms
activeview
140 ms
cTrvNaRi.html
20 ms
pixel
13 ms
activeview
14 ms
pixel
15 ms
main.js
224 ms
activeview
13 ms
activeview
14 ms
cms.national-geographic.pl 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 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
<frame> or <iframe> elements do not have a title
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.
cms.national-geographic.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
cms.national-geographic.pl SEO score
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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cms.national-geographic.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Cms.national-geographic.pl 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.
cms.national-geographic.pl
Open Graph description is not detected on the main page of Cms National Geographic. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: