8.2 sec in total
119 ms
1.7 sec
6.4 sec
Click here to check amazing Perry House content for United States. Otherwise, check out these important facts you probably never knew about perry.house.gov
Congressman Scott Perry Serving Pennsylvania's 10th Congressional District.
Visit perry.house.govWe analyzed Perry.house.gov page load time and found that the first response time was 119 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
perry.house.gov performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value3.8 s
55/100
25%
Value5.9 s
48/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.9 s
100/100
10%
119 ms
85 ms
74 ms
100 ms
182 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 51% of them (40 requests) were addressed to the original Perry.house.gov, 14% (11 requests) were made to Platform.twitter.com and 10% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (644 ms) belongs to the original domain Perry.house.gov.
Page size can be reduced by 1.3 MB (6%)
20.1 MB
18.8 MB
In fact, the total size of Perry.house.gov main page is 20.1 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. Only a small number of websites need less resources to load. Images take 19.6 MB which makes up the majority of the site volume.
Potential reduce by 60.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. This page needs HTML code to be minified as it can gain 14.9 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 60.6 kB or 82% of the original size.
Potential reduce by 1.2 MB
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. Perry House images are well optimized though.
Potential reduce by 47.5 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 47.5 kB or 13% of the original size.
Potential reduce by 3.6 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. Perry.house.gov has all CSS files already compressed.
Number of requests can be reduced by 24 (41%)
58
34
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Perry 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 from 4 to 1 for CSS and as a result speed up the page load time.
perry.house.gov
119 ms
css2
85 ms
main.css
74 ms
buffer.css
100 ms
js
182 ms
sdk.js
86 ms
api.js
85 ms
widgets.js
181 ms
jquery.min.js
68 ms
jquery.main.js
181 ms
jquery.fancybox.min.js
183 ms
0.jpg
81 ms
seal.png
272 ms
logo.svg
63 ms
887beb98-7591-4a18-a906-a1ef08ee394e.jpg
69 ms
f9b97641-6c50-4c12-8ced-95d13e7b9dff.jpg
72 ms
c2fdc59f-e5cf-433f-88b8-f9a0b6f6d20c.jpg
270 ms
72b7bda3-d2e0-4458-b221-9031dec63a3c.jpg
270 ms
63df26b5-58d4-4356-92c2-b9ef58c908f7.jpg
195 ms
5b176193-727f-4034-909a-10bf68c8651d.jpg
269 ms
789e264c-ef19-493b-a2b6-d865100d0f40.jpg
269 ms
496bfdd6-69c1-4deb-86ea-3a88a2309351.png
287 ms
5e793893-184d-4a09-bca0-8ed2d8a64f20.png
321 ms
eb3dcf28-edea-4dbc-a726-b5a8a7740c1a.jpg
321 ms
4f132379-a74d-4f4a-b040-e74a0bd569cb.jpg
321 ms
agriculture.jpg
331 ms
energy-rep.jpg
320 ms
immigration.jpg
336 ms
jobs.jpg
331 ms
security.jpg
331 ms
family.jpg
428 ms
gun-rep.jpg
398 ms
transportation.jpg
488 ms
veterans.jpg
488 ms
bio-photo.jpg
485 ms
0.jpg
67 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf
72 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf
267 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf
269 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf
269 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCP.ttf
268 ms
sdk.js
96 ms
recaptcha__en.js
185 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
229 ms
887beb98-7591-4a18-a906-a1ef08ee394e.jpg
428 ms
f9b97641-6c50-4c12-8ced-95d13e7b9dff.jpg
430 ms
310 ms
icomoon.ttf
301 ms
63df26b5-58d4-4356-92c2-b9ef58c908f7.jpg
396 ms
72b7bda3-d2e0-4458-b221-9031dec63a3c.jpg
398 ms
c2fdc59f-e5cf-433f-88b8-f9a0b6f6d20c.jpg
641 ms
789e264c-ef19-493b-a2b6-d865100d0f40.jpg
644 ms
5b176193-727f-4034-909a-10bf68c8651d.jpg
394 ms
anchor
77 ms
anchor
167 ms
settings
207 ms
496bfdd6-69c1-4deb-86ea-3a88a2309351.png
310 ms
4f132379-a74d-4f4a-b040-e74a0bd569cb.jpg
272 ms
5e793893-184d-4a09-bca0-8ed2d8a64f20.png
278 ms
eb3dcf28-edea-4dbc-a726-b5a8a7740c1a.jpg
272 ms
styles__ltr.css
5 ms
recaptcha__en.js
14 ms
UebCYnqdbF9ngI7DuCagEaT4xpR4mAb5pwZcsRDRe9I.js
113 ms
webworker.js
111 ms
logo_48.png
101 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
36 ms
recaptcha__en.js
36 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
10 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
11 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
12 ms
RepScottPerry
463 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
23 ms
runtime-b1c52fd0a13ead5fcf6b.js
46 ms
modules-96ebc7ac3ad66d681a3d.js
69 ms
main-babd9234dc048fb47339.js
83 ms
_app-a9c9f1a99e4414675fb1.js
109 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
114 ms
_buildManifest.js
127 ms
_ssgManifest.js
128 ms
perry.house.gov accessibility score
perry.house.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
perry.house.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 Perry.house.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 Perry.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.
perry.house.gov
Open Graph data is detected on the main page of Perry House. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: