6.9 sec in total
191 ms
6.5 sec
299 ms
Welcome to rec.gov homepage info - get ready to check Rec best content right away, or after learning these important things about rec.gov
We're here to help you dream up your next trip, figure out the details, and reserve experiences at over 3,600 facilities and 103,000 individual sites across the country.
Visit rec.govWe analyzed Rec.gov page load time and found that the first response time was 191 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
rec.gov performance score
name
value
score
weighting
Value12.9 s
0/100
10%
Value19.4 s
0/100
25%
Value17.6 s
0/100
10%
Value27,840 ms
0/100
30%
Value0.312
37/100
15%
Value78.5 s
0/100
10%
191 ms
68 ms
1025 ms
416 ms
50 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Rec.gov, 44% (19 requests) were made to Cdn.recreation.gov and 16% (7 requests) were made to Recreation.gov. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Cdn.recreation.gov.
Page size can be reduced by 74.2 kB (29%)
253.9 kB
179.7 kB
In fact, the total size of Rec.gov main page is 253.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. 70% of websites need less resources to load. CSS take 147.5 kB which makes up the majority of the site volume.
Potential reduce by 42.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 42.0 kB or 79% of the original size.
Potential reduce by 32.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 32.0 kB or 60% of the original size.
Potential reduce by 187 B
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. Rec.gov has all CSS files already compressed.
Number of requests can be reduced by 13 (72%)
18
5
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rec. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
rec.gov
191 ms
www.recreation.gov
68 ms
gtm.js
1025 ms
css2
416 ms
mapbox-gl.css
50 ms
mapbox-gl.js
344 ms
apple-pay-sdk.js
459 ms
vendor.2c78859512e5f590cc8d.css
208 ms
styles.f400502a086d89be8ce8.min.css
337 ms
vendor.8ac3f5947cbaad6fa4a3.min.js
1025 ms
bundle.8ac3f5947cbaad6fa4a3.min.js
364 ms
AP2476_efcd652e-17eb-42ca-9a80-ae1c148844cd_700.jpg
3169 ms
3a63a1b3-e897-11ea-96cd-2e76ee64004f_5b9a7f77-8c37-40c2-9bf5-635cb009bed0_700.jpg
3786 ms
3a4d2b97-e7cd-11ea-8710-eabd4664df5f_b3adee15-de40-4009-a5e9-4dfc1c517a03_700.jpg
3956 ms
9ebf15cd-e7d3-11ea-8710-eabd4664df5f_9e3fa6fe-d945-4f9a-886f-c9a63907f91e_700.jpg
4034 ms
92cbeceb-ebc7-11ea-98dd-e638fec87f2e_254f3bab-7cc6-482a-ada2-7aebc78227f0_700.jpg
4033 ms
0b7eb323-ebc7-11ea-98dd-e638fec87f2e_6c779044-6c71-4e64-99eb-a55385d9f597_700.jpg
4030 ms
TP31_3e071d11-61de-4aae-906e-4f9ad841365c_700.jpg
4025 ms
10089811_bf925c9a-2112-4a9a-8e1f-f432fffe1209_700.jpg
4021 ms
b2ce4e36-ebd2-11ea-b83f-6e0e43d29f74_670c1c54-082e-4740-a4e6-01e265a2d529_700.jpeg
4006 ms
b21dd85c-3e4f-11ec-ad6d-4209ca53ef89_3781d61d-e6ac-42d7-97d7-52e7cdde27e7_700.png
4327 ms
d21271e2-ec52-11ea-8045-369699f3be2d_361b4d86-53f0-4822-bd38-40ac71a3a56e_700.jpg
4317 ms
AP2439_3d633819-fd74-460e-b71b-b4ef8804dca9_700.jpg
4314 ms
4675328_c6ae428d-a3b0-4256-8851-050b2931b0b6_700.jpg
4316 ms
9e5a9e3b-ebc0-11ea-98dd-e638fec87f2e_f0f78808-d47a-463e-9053-3a01cae505b7_700.jpg
4313 ms
74098ae2-ebcf-11ea-b83f-6e0e43d29f74_33428565-54de-4150-bce2-554af4893f8e_700.jpg
4314 ms
3fe0d0df-ec5b-11ea-bcba-fa43c1aabce3_103ff235-acb8-4f5d-b98f-f9a98b079433_700.jpg
4331 ms
0422847b-e7d4-11ea-8710-eabd4664df5f_e2efbe20-e94e-426a-8890-ec52f1a01edc_700.jpg
4331 ms
242379_df16dfa1-da84-4669-bae1-b87fbc11f2a8_700.jpg
4330 ms
10207636_66a0bee6-ec01-4b26-a2a3-4fe34bf347f1_700.jpg
4329 ms
analytics.js
1017 ms
hotjar-2219619.js
1144 ms
js
620 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
542 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
667 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
678 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
679 ms
embed.js
813 ms
collect
116 ms
collect
388 ms
modules.2be88a2123e5e486752f.js
237 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
183 ms
generic1662486925027.js
126 ms
rec.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 IDs are not unique
rec.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
Page has valid source maps
rec.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
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 Rec.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 Rec.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.
rec.gov
Open Graph data is detected on the main page of Rec. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: