875 ms in total
108 ms
569 ms
198 ms
Welcome to search.foia.gov homepage info - get ready to check Search FOIA best content for United States right away, or after learning these important things about search.foia.gov
Visit search.foia.govWe analyzed Search.foia.gov page load time and found that the first response time was 108 ms and then it took 767 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
search.foia.gov performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value7.1 s
5/100
25%
Value3.2 s
92/100
10%
Value1,540 ms
13/100
30%
Value0.069
96/100
15%
Value14.7 s
8/100
10%
108 ms
157 ms
104 ms
130 ms
129 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Search.foia.gov, 88% (44 requests) were made to Foia.gov and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (178 ms) relates to the external source Foia.gov.
Page size can be reduced by 244.5 kB (52%)
466.3 kB
221.8 kB
In fact, the total size of Search.foia.gov main page is 466.3 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. 25% of websites need less resources to load. Javascripts take 236.7 kB which makes up the majority of the site volume.
Potential reduce by 17.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 17.3 kB or 76% of the original size.
Potential reduce by 39.6 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, Search FOIA needs image optimization as it can save up to 39.6 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 163.4 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 163.4 kB or 69% of the original size.
Potential reduce by 24.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. Search.foia.gov needs all CSS files to be minified and compressed as it can save up to 24.2 kB or 85% of the original size.
Number of requests can be reduced by 27 (56%)
48
21
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Search FOIA. 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 as a result speed up the page load time.
search.foia.gov
108 ms
www.foia.gov
157 ms
foia-style.css
104 ms
jquery-1.3.2.min.js
130 ms
jquery.qtip-1.0.0-rc3.min.js
129 ms
swfobject.js
21 ms
justiceiso.js
61 ms
foiareport.js
115 ms
FusionCharts.js
79 ms
foiaAjax.js
90 ms
tablehover.js
106 ms
Universal-Federated-Analytics-Min.1.0.js
153 ms
breakout.js
122 ms
bg-grad.jpg
47 ms
doj-top-logo.jpg
43 ms
foia-title-final.jpg
47 ms
home-data-glance.jpg
46 ms
question-icon.gif
48 ms
highlights-title.jpg
48 ms
reports-homepage-title.gif
68 ms
spotlight-title.gif
68 ms
logo-cfpb.jpg
69 ms
logo-usda.jpg
70 ms
logo-usaid.jpg
70 ms
logo-doi.jpg
71 ms
foia-footer.gif
95 ms
datagov-footer.gif
95 ms
opengov-footer.gif
95 ms
usaspending-footer.gif
94 ms
recoverygov-footer.gif
94 ms
analytics.js
37 ms
iframe_api
39 ms
Statistics
178 ms
bg-header.jpg
88 ms
tab-home_on.png
87 ms
tab-data_off.png
86 ms
tab-reports_off.png
85 ms
tab-find_off.png
88 ms
tab-about_off.png
111 ms
homepage-herobg.jpg
135 ms
learn-foia.png
110 ms
explore-foia.png
115 ms
line-shadow.jpg
116 ms
highlight-list-bg.jpg
135 ms
homereports-bg.gif
136 ms
hrtab-on.gif
143 ms
hrtab-off.gif
144 ms
rss-subscribe.gif
159 ms
collect
60 ms
www-widgetapi.js
37 ms
search.foia.gov accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
search.foia.gov 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
Page has valid source maps
search.foia.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
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Search.foia.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 Search.foia.gov main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
search.foia.gov
Open Graph description is not detected on the main page of Search FOIA. 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: