Tools & Wizards About Us
nato.int screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

nato.int

NATO - Homepage

Page Load Speed

39.1 sec in total

First Response

545 ms

Resources Loaded

27.9 sec

Page Rendered

10.6 sec

nato.int screenshot

About Website

Visit nato.int now to see the best up-to-date NATO content for United States and also check out these interesting facts you probably never knew about nato.int

Visit nato.int

Key Findings

We analyzed Nato.int page load time and found that the first response time was 545 ms and then it took 38.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

nato.int performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.406

24/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

nato.int

545 ms

main.css

735 ms

mediaelementplayer.min.css

359 ms

libs.js

1187 ms

libs2.js

679 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 65% of them (32 requests) were addressed to the original Nato.int, 6% (3 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (8.6 sec) relates to the external source Apis.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (16%)

Content Size

7.6 MB

After Optimization

6.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nato.int main page is 7.6 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 6.5 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 160.5 kB

  • Original 178.7 kB
  • After minification 112.0 kB
  • After compression 18.2 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. This page needs HTML code to be minified as it can gain 66.7 kB, which is 37% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 160.5 kB or 90% of the original size.

Image Optimization

-6%

Potential reduce by 421.3 kB

  • Original 6.5 MB
  • After minification 6.1 MB

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. NATO images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 490.7 kB

  • Original 733.6 kB
  • After minification 732.8 kB
  • After compression 242.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 490.7 kB or 67% of the original size.

CSS Optimization

-79%

Potential reduce by 157.1 kB

  • Original 198.9 kB
  • After minification 198.2 kB
  • After compression 41.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. Nato.int needs all CSS files to be minified and compressed as it can save up to 157.1 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (35%)

Requests Now

43

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NATO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

nato.int

nato.int

545 ms

main.css

main.css

735 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

359 ms

libs.js

libs.js

1187 ms

libs2.js

libs2.js

679 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

603 ms

bundle.js

bundle.js

678 ms

initialize.js

initialize.js

1146 ms

limelightjs-player.js

limelightjs-player.js

121 ms

limelightjs-player.js

limelightjs-player.js

37 ms

css

css

663 ms

css

css

619 ms

logo_EN.png

logo_EN.png

1838 ms

20170130_banner-declassified-menu.jpg

20170130_banner-declassified-menu.jpg

1824 ms

20140828_140828-banner-menu-what-is-nato.jpg

20140828_140828-banner-menu-what-is-nato.jpg

1825 ms

20160705_160705-banner-video-animation.jpg

20160705_160705-banner-video-animation.jpg

1844 ms

20160705_160705-banner-nato-on-the-map.jpg

20160705_160705-banner-nato-on-the-map.jpg

1805 ms

20170307_20170313_banner-sg-report-2016_EN.jpg

20170307_20170313_banner-sg-report-2016_EN.jpg

1824 ms

20140828_140828-banner-menu-ukraine-chronology.jpg

20140828_140828-banner-menu-ukraine-chronology.jpg

1823 ms

20141126_141128-russian-myth.jpg

20141126_141128-russian-myth.jpg

1824 ms

NR-banner-menu.jpg

NR-banner-menu.jpg

1868 ms

20110401_tv.jpg

20110401_tv.jpg

1868 ms

gtm.js

gtm.js

1734 ms

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

662 ms

MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf

MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf

630 ms

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

629 ms

icomoon.woff

icomoon.woff

629 ms

analytics.js

analytics.js

105 ms

fbevents.js

fbevents.js

3323 ms

collect

collect

822 ms

identity.js

identity.js

324 ms

1329839397061378

1329839397061378

3871 ms

collect

collect

8267 ms

client.js

client.js

8638 ms

20170905_170905-balt-air-policing2_rdax_775x517.jpg

20170905_170905-balt-air-policing2_rdax_775x517.jpg

5342 ms

20170802_170802-sg_rdax_375x213.jpg

20170802_170802-sg_rdax_375x213.jpg

5189 ms

20170904_170904-georgia-fire_rdax_375x213.jpg

20170904_170904-georgia-fire_rdax_375x213.jpg

5188 ms

20170523_banner-we-are-nato-376.jpg

20170523_banner-we-are-nato-376.jpg

500 ms

20170307_20170313_banner-sg-report-2016_EN-375x125.jpg

20170307_20170313_banner-sg-report-2016_EN-375x125.jpg

500 ms

20170130_banner-declassified-homepage.jpg

20170130_banner-declassified-homepage.jpg

499 ms

20170718_170728-NR-2_SWARM_WarLeaks_YT-PERDIX-_US-DoD_rdax_375x211.jpg

20170718_170728-NR-2_SWARM_WarLeaks_YT-PERDIX-_US-DoD_rdax_375x211.jpg

498 ms

20170901_170825a-harvey_rdax_375x213.jpg

20170901_170825a-harvey_rdax_375x213.jpg

2124 ms

20170710_170710-nac-visit-story--program-676x384_rdax_375x213.jpg

20170710_170710-nac-visit-story--program-676x384_rdax_375x213.jpg

282 ms

20170705_170705a-001_rdax_375x213.jpg

20170705_170705a-001_rdax_375x213.jpg

545 ms

20170626_170629-mod-programme_rdax_375x213.jpg

20170626_170629-mod-programme_rdax_375x213.jpg

545 ms

20170620_170620b-003_rdax_375x213.jpg

20170620_170620b-003_rdax_375x213.jpg

544 ms

slick.woff

slick.woff

635 ms

2071 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

1665 ms

Accessibility Review

nato.int accessibility score

72

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

nato.int best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

nato.int SEO score

73

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nato.int can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nato.int 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.

Social Sharing Optimization

nato.int

Open Graph description is not detected on the main page of NATO. 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: