2.8 sec in total
26 ms
2 sec
730 ms
Click here to check amazing Jordan House content for United States. Otherwise, check out these important facts you probably never knew about jordan.house.gov
Visit jordan.house.govWe analyzed Jordan.house.gov page load time and found that the first response time was 26 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
jordan.house.gov performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value14.1 s
0/100
25%
Value9.2 s
13/100
10%
Value640 ms
47/100
30%
Value0.041
99/100
15%
Value16.8 s
5/100
10%
26 ms
87 ms
26 ms
8 ms
71 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 49% of them (47 requests) were addressed to the original Jordan.house.gov, 18% (17 requests) were made to Maps.googleapis.com and 7% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Jordan.house.gov.
Page size can be reduced by 703.6 kB (36%)
2.0 MB
1.3 MB
In fact, the total size of Jordan.house.gov main page is 2.0 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. 65% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 34.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 34.6 kB or 83% of the original size.
Potential reduce by 38.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. Jordan House images are well optimized though.
Potential reduce by 593.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 593.0 kB or 70% of the original size.
Potential reduce by 37.1 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. Jordan.house.gov needs all CSS files to be minified and compressed as it can save up to 37.1 kB or 84% of the original size.
Number of requests can be reduced by 33 (38%)
86
53
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jordan House. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
jordan.house.gov
26 ms
all.2015.css
87 ms
css
26 ms
jquery.min.js
8 ms
jquery.zipform.min.js
71 ms
jquery.main.2015.js
110 ms
analytics.js
305 ms
embed
422 ms
embed
440 ms
embed
471 ms
embed
515 ms
bg-menu.png
137 ms
img-new.jpg
393 ms
logo.2015.png
93 ms
b6e47e06-52d7-4a27-81c3-0a61fe189cd5.jpg
132 ms
36a67cb9-fdc0-4edc-a558-1403b17c794f.jpg
212 ms
img4.jpg
317 ms
f44cfc1f-3905-4672-8ac4-dae0af6273d9.jpg
332 ms
dee04b8f-264b-4371-b518-6120cd01677e.jpg
332 ms
art-competition.png
585 ms
border.png
331 ms
img16.png
591 ms
img16-hover.png
585 ms
img17.png
523 ms
img17-hover.png
588 ms
img18.png
587 ms
img18-hover.png
585 ms
img19.png
646 ms
img19-hover.png
590 ms
img20.png
588 ms
img20-hover.png
744 ms
img21.png
590 ms
img21-hover.png
871 ms
img22.png
743 ms
img22-hover.png
743 ms
img23.png
878 ms
img23-hover.png
876 ms
img15.jpg
875 ms
img7.jpg
875 ms
img8.jpg
874 ms
img9.2015.jpg
1015 ms
img10.jpg
1013 ms
img11.jpg
1112 ms
img12.jpg
1013 ms
img13.jpg
1014 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
46 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
55 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
56 ms
icomoon.ttf
1011 ms
collect
23 ms
collect
18 ms
collect
41 ms
collect
41 ms
collect
57 ms
img14.jpg
1092 ms
b6e47e06-52d7-4a27-81c3-0a61fe189cd5.jpg
1293 ms
logo2.png
991 ms
js
54 ms
init_embed.js
41 ms
0ae7664f-3fbf-401f-8b8c-ac0ab6806a64.jpg
1007 ms
36a67cb9-fdc0-4edc-a558-1403b17c794f.jpg
916 ms
common.js
54 ms
map.js
112 ms
google4.png
47 ms
overlay.js
79 ms
util.js
76 ms
onion.js
74 ms
search_impl.js
74 ms
close.png
1158 ms
dee04b8f-264b-4371-b518-6120cd01677e.jpg
1157 ms
f44cfc1f-3905-4672-8ac4-dae0af6273d9.jpg
1158 ms
stats.js
115 ms
openhand_8_8.cur
106 ms
ViewportInfoService.GetViewportInfo
175 ms
controls.js
15 ms
ViewportInfoService.GetViewportInfo
52 ms
transparent.png
49 ms
kh
272 ms
ViewportInfoService.GetViewportInfo
254 ms
ViewportInfoService.GetViewportInfo
234 ms
kh
379 ms
kh
374 ms
kh
238 ms
css
581 ms
entity11.png
173 ms
ViewportInfoService.GetViewportInfo
156 ms
ViewportInfoService.GetViewportInfo
119 ms
ViewportInfoService.GetViewportInfo
157 ms
ViewportInfoService.GetViewportInfo
142 ms
kh
181 ms
kh
181 ms
kh
179 ms
kh
582 ms
kh
583 ms
mapcnt6.png
408 ms
sv5.png
579 ms
jordan.house.gov accessibility score
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-*] attributes do not have valid values
jordan.house.gov 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
jordan.house.gov 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jordan.house.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 Jordan.house.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.
jordan.house.gov
Open Graph description is not detected on the main page of Jordan House. 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: