661 ms in total
61 ms
451 ms
149 ms
Visit vault.fbi.gov now to see the best up-to-date Vault FBI content for United States and also check out these interesting facts you probably never knew about vault.fbi.gov
Visit vault.fbi.govWe analyzed Vault.fbi.gov page load time and found that the first response time was 61 ms and then it took 600 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
vault.fbi.gov performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value3.6 s
60/100
25%
Value2.3 s
99/100
10%
Value110 ms
97/100
30%
Value0.991
2/100
15%
Value4.8 s
78/100
10%
61 ms
12 ms
23 ms
30 ms
27 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 90% of them (35 requests) were addressed to the original Vault.fbi.gov, 5% (2 requests) were made to Gateway.answerscloud.com and 3% (1 request) were made to Translate.google.com. The less responsive or slowest element that took the longest time to load (122 ms) relates to the external source Translate.google.com.
Page size can be reduced by 150.1 kB (52%)
287.9 kB
137.8 kB
In fact, the total size of Vault.fbi.gov main page is 287.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 142.0 kB which makes up the majority of the site volume.
Potential reduce by 22.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 22.0 kB or 72% of the original size.
Potential reduce by 36.0 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, Vault FBI needs image optimization as it can save up to 36.0 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 92.0 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 92.0 kB or 65% of the original size.
Number of requests can be reduced by 18 (47%)
38
20
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vault FBI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
vault.fbi.gov
61 ms
base-cachekey-60b4895ed26ecf93062af9ad6bf721c1.css
12 ms
columns-cachekey-fcc658e43b6c10b73b9de60667d3a504.css
23 ms
resourcetinymce.stylesheetstinymce-cachekey-ed5cb154e6c70f484eefd4817dd63d65.css
30 ms
print-cachekey-1ca41f5570e672977c2f68ce28da315c.css
27 ms
resourceContentWellPortlets.stylesContentWellPortlets-cachekey-675826adbbffd27ff4db7ef6b5b15b67.css
24 ms
resourceeasyslider-portlet-cachekey-035af662ff1e59666588713b0a419130.css
15 ms
fbi_custom-cachekey-658f66269531f29a5ae6288c621e762b.css
35 ms
resourcevideostylesvideo-cachekey-06ecac1a1ff3aa0e3617a63ffde8730d.css
18 ms
resourceplonetruegallery-portlet-cachekey-fd23734cfd3aebf90a7fd2506a8c91a1.css
24 ms
template_default-cachekey-821fcfefab90ade0cb96ab8bda09e3f9.css
29 ms
ploneCustom.css
27 ms
jquery-cachekey-5c56dfa7aece6fcb3992bcdbe7c80326.js
40 ms
resourceeasyslider-portlet-cachekey-cb8bd193f204fc002e50a8029212c3a4.js
58 ms
resourceplonetheme.fbi.javascriptsjquery.media-cachekey-f7960ffd16dcc6996e33ad0a821e995a.js
60 ms
foreseeforesee-alive-cachekey-81c52ab713c610b43fc7fb9b16de5a2a.js
60 ms
resourcejsi18n-cachekey-ae505473006c1056bf6bcfd0e88826b2.js
58 ms
urchin.js
53 ms
gateway.min.js
114 ms
foia-disclaimer-text
42 ms
element.js
122 ms
reportthreats.png
52 ms
az.png
50 ms
sitemap.png
49 ms
input_background.gif
48 ms
search.png
50 ms
logo1.png
51 ms
logo2.png
51 ms
logo3.png
66 ms
nav-sprite.gif
64 ms
bg-nav-left-edge-trans.png
109 ms
bg-nav-right-edge-trans.png
65 ms
vault-banner.jpg
70 ms
mail.png
63 ms
image_large
72 ms
line60.jpg
85 ms
spinner.gif
87 ms
__utm.gif
74 ms
foresee_trigger.js
22 ms
vault.fbi.gov 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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
vault.fbi.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
vault.fbi.gov 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vault.fbi.gov 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 Vault.fbi.gov 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.
vault.fbi.gov
Open Graph description is not detected on the main page of Vault FBI. 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: