6.6 sec in total
327 ms
6 sec
276 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 327 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
nationalgeographic.com.tr performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value14.8 s
0/100
25%
Value13.9 s
1/100
10%
Value600 ms
49/100
30%
Value0
100/100
15%
Value16.6 s
5/100
10%
327 ms
966 ms
258 ms
258 ms
262 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 14% of them (13 requests) were addressed to the original Nationalgeographic.com.tr, 66% (63 requests) were made to Static.nationalgeographic.com.tr and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Mc.yandex.ru.
Page size can be reduced by 2.0 MB (52%)
4.0 MB
1.9 MB
In fact, the total size of Nationalgeographic.com.tr main page is 4.0 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. Javascripts take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 52.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 52.0 kB or 43% of the original size.
Potential reduce by 36.8 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. National Geographic images are well optimized though.
Potential reduce by 1.7 MB
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 1.7 MB or 70% of the original size.
Potential reduce by 281.2 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. Nationalgeographic.com.tr needs all CSS files to be minified and compressed as it can save up to 281.2 kB or 83% of the original size.
Number of requests can be reduced by 44 (51%)
87
43
The browser has sent 87 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 29 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
nationalgeographic.com.tr
327 ms
www.nationalgeographic.com.tr
966 ms
Reset.min.css
258 ms
Fonts.min.css
258 ms
Common.min.css
262 ms
Animations.min.css
265 ms
Header.min.css
266 ms
Footer.min.css
276 ms
PopUps.min.css
380 ms
LoggedIn.min.css
381 ms
URI.min.js
251 ms
royalslider.min.css
388 ms
rs-minimal-white.min.css
387 ms
kendo.common.min.css
394 ms
kendo.dataviz.min.css
410 ms
kendo.metro.min.css
502 ms
kendo.dataviz.metro.min.css
505 ms
jquery-1.11.0.min.js
641 ms
jquery-migrate-1.2.1.min.js
515 ms
modernizr-2.7.2.min.js
524 ms
kendo.all.min.js
2051 ms
kendo.aspnetmvc.min.js
626 ms
kendo.culture.tr-TR.min.js
629 ms
css
71 ms
bulten.css
250 ms
jquery.fancybox.css
256 ms
jquery.fancybox.js
268 ms
watermark.js
276 ms
popup-newsletter.js
362 ms
dyg_base-v2.js
577 ms
respond.min.js
339 ms
Common.min.js
340 ms
Default.min.js
406 ms
jquery.royalslider.min.js
534 ms
jquery.unobtrusive-ajax.min.js
423 ms
jquery.validate.min.js
425 ms
jquery.validate.unobtrusive.min.js
439 ms
jquery.validate.custom.min.js
531 ms
jquery.placeholder.min.js
551 ms
pi.js
274 ms
analytics.js
85 ms
watch.js
239 ms
gpt.js
72 ms
NG.js
145 ms
swfobject.js
502 ms
logo.png
142 ms
sociallg.png
178 ms
facebookx.png
176 ms
twitterx.png
171 ms
instagramx.png
174 ms
newsletterx.png
176 ms
googlex.png
168 ms
sociallb.png
486 ms
newsletterw.png
487 ms
googlew.png
525 ms
instagramw.png
525 ms
twitterw.png
523 ms
facebookw.png
523 ms
search.png
522 ms
stickedlogo.png
522 ms
insta_banner.jpg
934 ms
2742_m.jpg
907 ms
2741_m.jpg
898 ms
2740_m.jpg
907 ms
2j2iqy1m.jpg
1446 ms
2745_m.jpg
647 ms
2724_m.jpg
773 ms
kutup-multecileri.jpg
1027 ms
2725_m.jpg
1022 ms
2735_m.jpg
1036 ms
2744_m.jpg
1034 ms
logo-lb.png
165 ms
content.jpg
170 ms
nat-geo-logo.png
163 ms
smallarrowy.png
1038 ms
arowy.png
1118 ms
article-show.png
1124 ms
mask1.png
1134 ms
arowgx.png
1134 ms
downarrowb.png
1174 ms
goup.png
1243 ms
AkzidenzGroteskBE.ttf
1160 ms
AkzidenzGroteskBEMd.ttf
1299 ms
IRFxB2matTxrjZt6a3FUnnQfGerycEmjzUuht-RqCuQ.ttf
355 ms
T2vUYmWzlqUtgLYdlemGnabjVLFmJPd7jBen3mFxMo8.ttf
396 ms
qHqW2lwKO8-uTfIkh8FsUd3CFc22EOj34-ODC_S0U0g.ttf
422 ms
632u7TMIoFDWQYUaHFUp5KpiUv6weKNvmXjvbS_aNrs.ttf
435 ms
pubads_impl_81.js
42 ms
collect
42 ms
container.html
279 ms
watch.js
2488 ms
pi.aspx
343 ms
btn-close.png
288 ms
ads
160 ms
session
186 ms
sync
29 ms
nationalgeographic.com.tr accessibility score
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
nationalgeographic.com.tr 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
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 uses legible font sizes
Tap targets are not sized appropriately
TR
EN
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 does not match the claimed English 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 description is not detected on the main page of 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: