45.8 sec in total
2.1 sec
28.1 sec
15.5 sec
Click here to check amazing Fas content for United States. Otherwise, check out these important facts you probably never knew about fas.org
FAS envisions a world where cutting-edge science, technology, ideas and talent are deployed to solve the biggest challenges of our time.
Visit fas.orgWe analyzed Fas.org page load time and found that the first response time was 2.1 sec and then it took 43.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
fas.org performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value21.5 s
0/100
25%
Value11.2 s
5/100
10%
Value780 ms
37/100
30%
Value0.094
91/100
15%
Value23.8 s
1/100
10%
2102 ms
274 ms
315 ms
1680 ms
1991 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 61% of them (56 requests) were addressed to the original Fas.org, 11% (10 requests) were made to Google.com and 9% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (9.5 sec) relates to the external source Google.com.
Page size can be reduced by 2.0 MB (42%)
4.7 MB
2.7 MB
In fact, the total size of Fas.org main page is 4.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. 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 2.1 MB which makes up the majority of the site volume.
Potential reduce by 56.6 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 56.6 kB or 77% of the original size.
Potential reduce by 300.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. Obviously, Fas needs image optimization as it can save up to 300.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 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.1 MB or 59% of the original size.
Potential reduce by 563.9 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. Fas.org needs all CSS files to be minified and compressed as it can save up to 563.9 kB or 81% of the original size.
Number of requests can be reduced by 41 (51%)
81
40
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
fas.org
2102 ms
wp-emoji-release.min.js
274 ms
public.css
315 ms
bootstrap.min.css
1680 ms
font-awesome.min.css
1991 ms
css
2433 ms
style.css
1052 ms
royalslider.css
1520 ms
rs-universal.css
1851 ms
rs-content-slider-template.css
1519 ms
jquery-ui-1.11.4.custom.css
1519 ms
mediaelementplayer.min.css
1850 ms
wp-mediaelement.min.css
1989 ms
wpv-pagination.css
2122 ms
jquery.js
2122 ms
jquery-migrate.min.js
2028 ms
jquery.tools.min.js
2028 ms
affix.js
2279 ms
custom_script.js
2828 ms
adsbygoogle.js
2334 ms
classic-10_7.css
3082 ms
mc-validate.js
3211 ms
bootstrap.min.js
2026 ms
core.min.js
3156 ms
datepicker.min.js
3156 ms
mediaelement-and-player.min.js
3155 ms
wp-mediaelement.min.js
3098 ms
underscore.min.js
3098 ms
wp-util.min.js
3098 ms
backbone.min.js
3287 ms
wp-playlist.min.js
3288 ms
wpv-pagination-embedded.js
3286 ms
wp-embed.min.js
3286 ms
jquery.royalslider.min.js
3285 ms
fas_logo.png
627 ms
logo_dark.png
967 ms
Mailchimp-FAS-Roundup-Banner-1024x410.png
723 ms
datalock1-230x100.jpg
625 ms
nuclearweapons31-230x100.jpg
721 ms
radiation-cask-1-230x100.jpg
716 ms
radiationdanger-230x100.jpg
670 ms
microscope-230x100.jpg
812 ms
energy1-230x100.jpg
813 ms
3d-map-of-Iran-150x150.jpg
668 ms
Iran-150x150.jpg
660 ms
syriaflag-150x150.jpg
769 ms
blogs-cdn.fas_.org-wp-content-uploads-2013-10-The_MANPADS_Threat1-150x150.png
771 ms
blogs-cdn.fas_.org-wp-content-uploads-2013-05-Regulating_Japanese_Nuclear_13May13.pdf-150x150.png
769 ms
USJapanNukeReportApril2013-150x150.jpg
771 ms
blogs-cdn.fas_.org-wp-content-uploads-2013-04-iran_nuclear_odyssey-150x150.png
764 ms
www.fas_.org-programs-ssp-nukes-publications1-TrimmingNuclearExces-150x150.png
755 ms
www.fas_.org-_docs-2012IssueBrief_Japan.pdf-150x150.png
852 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
3114 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
7627 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
7869 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
7869 ms
ca-pub-6837127770928289.js
425 ms
zrt_lookup.html
8586 ms
show_ads_impl.js
2734 ms
cse.js
9475 ms
fontawesome-webfont.woff
9091 ms
ads
5521 ms
osd.js
2657 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
2779 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
2779 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
2779 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
2779 ms
ads
1721 ms
cse.js
1968 ms
jsapi
62 ms
analytics.js
1636 ms
admin-ajax.php
2899 ms
admin-ajax.php
2615 ms
default+en.css
186 ms
default.css
287 ms
default+en.I.js
376 ms
collect
1024 ms
www.fas_.org-_docs-2012_Iran_and_Global_Economy-150x150.png
416 ms
www.fas_.org-pubs-_docs-IssueBrief-Sanctions.pdf-150x150.png
141 ms
www.fas_.org-pubs-_docs-Nuclear_Energy_Report-lowres-150x150.png
645 ms
www.fas_.org-pubs-_docs-20110926_Nuclear_Free_Mirage.pdf-150x150.png
645 ms
www.fas_.org-pubs-_docs-Terrorism_Analysis_Report_1-lowres-150x150.png
2993 ms
nuclear-city-150x150.jpg
644 ms
terrorist-150x150.jpg
644 ms
nuclearexplosion-150x150.jpg
644 ms
shutterstock_152202584-150x150.jpg
2991 ms
async-ads.js
2202 ms
googlelogo_lightgrey_46x16dp.png
2199 ms
googlelogo_grey_46x15dp.png
258 ms
search_box_icon.png
1188 ms
clear.png
1295 ms
nav_logo114.png
1294 ms
fas.org 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
[id] attributes on active, focusable elements are not unique
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 IDs are not unique
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
fas.org 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
Missing source maps for large first-party JavaScript
fas.org 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fas.org 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 Fas.org 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.
fas.org
Open Graph description is not detected on the main page of Fas. 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: