6.5 sec in total
190 ms
6.2 sec
154 ms
Click here to check amazing Rea Project content for United States. Otherwise, check out these important facts you probably never knew about reaproject.org
Using the interactive regional economic tools of analysis at your disposal on this website, conduct your own research about changing local economic conditions and trends throughout the United States.
Visit reaproject.orgWe analyzed Reaproject.org page load time and found that the first response time was 190 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
reaproject.org performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value4.8 s
31/100
25%
Value4.4 s
73/100
10%
Value480 ms
59/100
30%
Value0.015
100/100
15%
Value6.9 s
53/100
10%
190 ms
1965 ms
278 ms
385 ms
280 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 98% of them (84 requests) were addressed to the original Reaproject.org, 2% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Reaproject.org.
Page size can be reduced by 137.5 kB (16%)
871.2 kB
733.7 kB
In fact, the total size of Reaproject.org main page is 871.2 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. 40% of websites need less resources to load. Images take 658.0 kB which makes up the majority of the site volume.
Potential reduce by 41.1 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 41.1 kB or 78% of the original size.
Potential reduce by 27 B
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. Rea Project images are well optimized though.
Potential reduce by 80.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 80.5 kB or 57% of the original size.
Potential reduce by 15.9 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. Reaproject.org needs all CSS files to be minified and compressed as it can save up to 15.9 kB or 80% of the original size.
Number of requests can be reduced by 9 (11%)
84
75
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rea Project. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
reaproject.org
190 ms
www.reaproject.org
1965 ms
reap-homepage.min.css
278 ms
jquery-1.10.2.min.js
385 ms
jquery.split.sticky.header.min.js
280 ms
layout.min.js
284 ms
region-page.min.js
281 ms
bea-top-menu.min.js
295 ms
region-homepage.min.js
371 ms
research-menu.min.js
371 ms
reap-homepage.min.js
372 ms
reap-analysis-banner.min.js
376 ms
dc.js
80 ms
reap_bottom_bg.jpg
110 ms
reap_top_bg.jpg
91 ms
large-reap-icon.png
102 ms
reap_logo.png
107 ms
REAP.png
105 ms
hosted_reaps.png
370 ms
Brought_to_You_By.png
185 ms
pnreap_logo.png
197 ms
hosted_reaps.png
777 ms
scheduled.json
684 ms
reap_regional_analysis.png
258 ms
map_0.png
677 ms
map_0_0_C1.png
601 ms
map_0_10000_C1.png
505 ms
map_0_20000_C1.png
506 ms
map_0_40000_C1.png
741 ms
map_0_50000_C1.png
749 ms
map_0_60000_C1.png
781 ms
map_0_80000_C1.png
877 ms
map_0_90000_C1.png
1027 ms
map_0_100000_C1.png
976 ms
map_0_110000_C1.png
1048 ms
map_0_120000_C1.png
1033 ms
map_0_130000_C1.png
1068 ms
map_0_150000_C1.png
1073 ms
map_0_160000_C1.png
1164 ms
map_0_170000_C1.png
1268 ms
map_0_180000_C1.png
1291 ms
map_0_190000_C1.png
1269 ms
map_0_200000_C1.png
1322 ms
map_0_210000_C1.png
1313 ms
map_0_220000_C1.png
1341 ms
map_0_230000_C1.png
1504 ms
map_0_240000_C1.png
1553 ms
map_0_250000_C1.png
1565 ms
map_0_260000_C1.png
1559 ms
__utm.gif
11 ms
map_0_270000_C1.png
1545 ms
map_0_280000_C1.png
1531 ms
map_0_290000_C1.png
1723 ms
map_0_300000_C1.png
1854 ms
map_0_310000_C1.png
1879 ms
map_0_320000_C1.png
1803 ms
map_0_330000_C1.png
1800 ms
map_0_340000_C1.png
1669 ms
map_0_350000_C1.png
1694 ms
map_0_360000_C1.png
1713 ms
map_0_370000_C1.png
1789 ms
map_0_380000_C1.png
1646 ms
map_0_390000_C1.png
1586 ms
map_0_400000_C1.png
1607 ms
map_0_410000_C1.png
1572 ms
map_0_420000_C1.png
1678 ms
map_0_440000_C1.png
1809 ms
map_0_450000_C1.png
1809 ms
map_0_460000_C1.png
1746 ms
map_0_470000_C1.png
1647 ms
map_0_480000_C1.png
1598 ms
map_0_490000_C1.png
1624 ms
map_0_500000_C1.png
1847 ms
map_0_510000_C1.png
1872 ms
map_0_530000_C1.png
1894 ms
map_0_540000_C1.png
1798 ms
map_0_550000_C1.png
1698 ms
map_0_560000_C1.png
1699 ms
map_0_910000_C1.png
1915 ms
map_0_920000_C1.png
1999 ms
map_0_930000_C1.png
2039 ms
map_0_940000_C1.png
2021 ms
map_0_950000_C1.png
1931 ms
map_0_960000_C1.png
1815 ms
map_0_970000_C1.png
1857 ms
map_0_980000_C1.png
1953 ms
reaproject.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
reaproject.org 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
reaproject.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Reaproject.org 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 Reaproject.org 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.
reaproject.org
Open Graph data is detected on the main page of Rea Project. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: