738 ms in total
57 ms
603 ms
78 ms
Visit recalls.gov now to see the best up-to-date Recalls content for United States and also check out these interesting facts you probably never knew about recalls.gov
Recalls.gov: official U.S. Government website, including recalls from various Federal Agencies
Visit recalls.govWe analyzed Recalls.gov page load time and found that the first response time was 57 ms and then it took 681 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.
recalls.gov performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value2.3 s
93/100
25%
Value1.9 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.9 s
100/100
10%
57 ms
33 ms
29 ms
28 ms
30 ms
Our browser made a total of 20 requests to load all elements on the main page. We found that all of those requests were addressed to Recalls.gov and no external sources were called. The less responsive or slowest element that took the longest time to load (80 ms) belongs to the original domain Recalls.gov.
Page size can be reduced by 9.6 kB (4%)
262.0 kB
252.4 kB
In fact, the total size of Recalls.gov main page is 262.0 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. 15% of websites need less resources to load. Images take 255.3 kB which makes up the majority of the site volume.
Potential reduce by 4.7 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 4.7 kB or 70% of the original size.
Potential reduce by 4.9 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. Recalls images are well optimized though.
We found no issues to fix!
19
19
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Recalls. According to our analytics all requests are already optimized.
{{url}}
{{time}} ms
recalls.gov accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
recalls.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
recalls.gov SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Recalls.gov 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 Recalls.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.
{{og_description}}
recalls.gov
Open Graph description is not detected on the main page of Recalls. 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: