3.4 sec in total
231 ms
2.6 sec
630 ms
Visit oregon.gov now to see the best up-to-date Oregon content for United States and also check out these interesting facts you probably never knew about oregon.gov
The official homepage of the State of Oregon
Visit oregon.govWe analyzed Oregon.gov page load time and found that the first response time was 231 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
oregon.gov performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value6.3 s
10/100
25%
Value12.3 s
3/100
10%
Value6,520 ms
0/100
30%
Value1.054
2/100
15%
Value14.0 s
10/100
10%
231 ms
6 ms
25 ms
8 ms
113 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 38% of them (30 requests) were addressed to the original Oregon.gov, 10% (8 requests) were made to Scontent.cdninstagram.com and 10% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Scontent.cdninstagram.com.
Page size can be reduced by 1.4 MB (26%)
5.4 MB
4.0 MB
In fact, the total size of Oregon.gov main page is 5.4 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 3.5 MB which makes up the majority of the site volume.
Potential reduce by 124.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. This page needs HTML code to be minified as it can gain 30.3 kB, which is 21% 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 124.1 kB or 85% of the original size.
Potential reduce by 96.5 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. Oregon images are well optimized though.
Potential reduce by 827.8 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 827.8 kB or 63% of the original size.
Potential reduce by 382.5 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. Oregon.gov needs all CSS files to be minified and compressed as it can save up to 382.5 kB or 82% of the original size.
Number of requests can be reduced by 42 (58%)
73
31
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oregon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
index.aspx
231 ms
font-awesome.min.css
6 ms
css
25 ms
font-awesome.min.css
8 ms
portal2015.css
113 ms
portal2.css
150 ms
modernizr-2.6.2-respond-1.1.0.min.js
227 ms
WebResource.axd
112 ms
blank.js
82 ms
bootstrap.min.css
67 ms
snapwidget.js
96 ms
element.js
76 ms
jquery.min.js
318 ms
js
88 ms
bundle-min.js
390 ms
orgov-min.js
193 ms
portal-min.js
280 ms
init.js
251 ms
mavention.sharepoint.insertsymbol.loader.js
149 ms
ScriptResource.axd
88 ms
ScriptResource.axd
126 ms
portal-bg2.jpg
519 ms
walking_squatch.gif
49 ms
home_map_graphic-lg.jpeg
219 ms
OSL_Oregonbday.png
161 ms
DOR_kicker2016.png
219 ms
stop_cycle.png
112 ms
feature_story_OEM_flood.png
198 ms
payments_feature.jpg
160 ms
forms_feature.jpg
218 ms
licenses_feature.jpg
198 ms
driver.jpg
247 ms
bow.png
246 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
17 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
16 ms
orgov_logo_color.png
227 ms
cse.js
62 ms
fontawesome-webfont.woff
26 ms
fontawesome-webfont.woff
26 ms
210 ms
translateelement.css
72 ms
main.js
75 ms
jsapi
27 ms
default+en.css
5 ms
default.css
36 ms
default+en.I.js
13 ms
default.css
41 ms
element_main.js
66 ms
jquery-1.10.2.min.js
164 ms
combined.css
17 ms
smoothDivScroll.css
7 ms
iframeresize.js
7 ms
jquery.min.js
8 ms
analytics.js
20 ms
12132701_760868947372210_792174274_n.jpg
513 ms
11906277_1010086195678249_694652446_n.jpg
679 ms
12256642_139772566383321_1779642592_n.jpg
876 ms
12224597_970319659657264_1122804786_n.jpg
1012 ms
12269832_562201637263856_554207779_n.jpg
879 ms
11939462_1669306519982510_1559936906_n.jpg
946 ms
12237413_1652700938342313_1671991938_n.jpg
747 ms
12132718_1492168641111696_1293987095_n.jpg
813 ms
collect
3 ms
collect
156 ms
collect
2 ms
ga.js
61 ms
async-ads.js
33 ms
google-search.png%E2%80%9D
333 ms
small-logo.png
29 ms
search_box_icon.png
31 ms
clear.png
55 ms
__utm.gif
23 ms
translate_24dp.png
36 ms
l
43 ms
cleardot.gif
29 ms
te_ctrl3.gif
11 ms
nr-852.min.js
18 ms
core.js
151 ms
a53393d12f
53 ms
oregon.gov accessibility score
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
Links do not have a discernible name
oregon.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
Missing source maps for large first-party JavaScript
oregon.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 doesn't use 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 Oregon.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 Oregon.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.
oregon.gov
Open Graph description is not detected on the main page of Oregon. 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: