3.3 sec in total
94 ms
2.7 sec
557 ms
Click here to check amazing National Geographic content for Turkey. Otherwise, check out these important facts you probably never knew about nationalgeographic.com.tr
Bilimin ve keşfin öncüsü National Geographic ile daha ötesini keşfet.
Visit nationalgeographic.com.trWe analyzed Nationalgeographic.com.tr page load time and found that the first response time was 94 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
nationalgeographic.com.tr performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value7.0 s
6/100
25%
Value6.4 s
41/100
10%
Value1,920 ms
8/100
30%
Value0
100/100
15%
Value9.5 s
30/100
10%
94 ms
167 ms
629 ms
32 ms
53 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Nationalgeographic.com.tr, 58% (26 requests) were made to Sire-media-ngctr.fichub.com and 13% (6 requests) were made to Natgeotv.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Sire-media-ngctr.fichub.com.
Page size can be reduced by 276.2 kB (11%)
2.4 MB
2.2 MB
In fact, the total size of Nationalgeographic.com.tr main page is 2.4 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. 50% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 274.3 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 274.3 kB or 66% of the original size.
Potential reduce by 0 B
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. National Geographic images are well optimized though.
Potential reduce by 1.9 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.
Number of requests can be reduced by 10 (24%)
42
32
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 11 to 1 for JavaScripts and as a result speed up the page load time.
nationalgeographic.com.tr
94 ms
tr
167 ms
tr
629 ms
otSDKStub.js
32 ms
31dd6abf-d314-4b24-b17e-f7980e299f6a.json
53 ms
location
58 ms
otBannerSdk.js
32 ms
age-verification.js
207 ms
687268.640x640.jpg
845 ms
jquery.min.js
60 ms
foundation.js
153 ms
exit_popup.js
190 ms
vendors-main.js
167 ms
acilia-main.js
165 ms
677339.600x338.jpg
531 ms
30465.600x338.jpg
490 ms
683059.640x360.jpg
493 ms
687271.600x338.jpg
462 ms
679395.600x338.jpg
841 ms
652989.600x338.jpg
549 ms
677908.600x338.jpg
584 ms
634381.640x360.jpg
671 ms
629144.600x338.jpg
1115 ms
676054.600x338.jpg
637 ms
644285.600x338.jpg
694 ms
674147.600x338.jpg
795 ms
icons.svg
96 ms
logos.svg
179 ms
natgeoBG.png
278 ms
mapping169_big.png
278 ms
picturefill.min.js
47 ms
gtm.js
84 ms
687268.1200x675.jpg
1011 ms
677339.1024x576.jpg
968 ms
30465.1024x576.jpg
1097 ms
683059.1200x675.jpg
1347 ms
687271.1024x576.jpg
692 ms
679395.1024x576.jpg
712 ms
652989.1024x576.jpg
726 ms
677908.1024x576.jpg
828 ms
634381.1200x675.jpg
1316 ms
629144.1024x576.jpg
1413 ms
676054.1024x576.jpg
1487 ms
644285.1024x576.jpg
1491 ms
674147.1024x576.jpg
1267 ms
nationalgeographic.com.tr 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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
nationalgeographic.com.tr 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
Browser errors were logged to the console
nationalgeographic.com.tr 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 doesn't use legible font sizes
Tap targets are not sized appropriately
TR
TR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nationalgeographic.com.tr can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and it matches the claimed language. Our system also found out that Nationalgeographic.com.tr 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.
nationalgeographic.com.tr
Open Graph data is detected on the main page of National Geographic. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: