3.5 sec in total
269 ms
2.8 sec
394 ms
Click here to check amazing Data Oregon content for United States. Otherwise, check out these important facts you probably never knew about data.oregon.gov
Visit data.oregon.govWe analyzed Data.oregon.gov page load time and found that the first response time was 269 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.
data.oregon.gov performance score
name
value
score
weighting
Value25.3 s
0/100
10%
Value48.1 s
0/100
25%
Value25.3 s
0/100
10%
Value7,340 ms
0/100
30%
Value0.705
7/100
15%
Value45.4 s
0/100
10%
269 ms
885 ms
170 ms
253 ms
270 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 61% of them (34 requests) were addressed to the original Data.oregon.gov, 23% (13 requests) were made to Use.typekit.net and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (969 ms) belongs to the original domain Data.oregon.gov.
Page size can be reduced by 900.7 kB (61%)
1.5 MB
577.0 kB
In fact, the total size of Data.oregon.gov main page is 1.5 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. 45% of websites need less resources to load. Javascripts take 915.1 kB which makes up the majority of the site volume.
Potential reduce by 127.7 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 127.7 kB or 77% of the original size.
Potential reduce by 2.7 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. Data Oregon images are well optimized though.
Potential reduce by 608.2 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 608.2 kB or 66% of the original size.
Potential reduce by 162.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. Data.oregon.gov needs all CSS files to be minified and compressed as it can save up to 162.1 kB or 86% of the original size.
Number of requests can be reduced by 14 (32%)
44
30
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Data 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 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
data.oregon.gov
269 ms
data.oregon.gov
885 ms
base.css
170 ms
socrata-apps.css
253 ms
errors.js
270 ms
components.css
257 ms
wsq6vdv.js
379 ms
current_site.css
303 ms
mixpanel-analytics.js
303 ms
base.js
669 ms
canvas.js
503 ms
yua8nhg.js
223 ms
jquery.min.js
95 ms
data.oregon.gov
102 ms
analytics.js
108 ms
orgov_logo_color.png
339 ms
D356C77B-54EF-4FEF-BAF0-F9D8A0D88D75
177 ms
0950B97B-5AC0-4619-A128-C6EB40CF2B69
108 ms
MKp3cS4XNyf3SDaF9tHxMmXCxAO5R6VcYiGF_YkjH2U
534 ms
S1trFcYlUQngZyDM5CoG066ti3h0Qj2cUssDAyEsJe8
159 ms
8d4R5JJ6N06bTOXo-dnjX07u-gPi-TrSo8-K1HPa4so
202 ms
6-MVYoBcR4nL2VvLfEPoyo4CiOvAjX5e4VxU4kovQwY
846 ms
X8hO4TJTOnnbPTe0uT_ipXYczNNA7aNsTFjC6ZvKK8w
375 ms
KzYRRLKotEb3J3xM7pXBQO9FpbVsHOTHTem3JdZWvx4
969 ms
jFD_xqS3mtBFDQAgF6iCKAk2nyrxaI-7ERFken5KWKg
421 ms
4LuI9JqWczgHAD7i9dE2Dms2Bbu-c0MoyqoyE1mQV8g
441 ms
rjpFe5g2g2P9sj0Bmp6RINhtDzI3bbiATCQGsX5nVJE
532 ms
_Q5I2JexsgpCVCAXMNRmLG0N9-dRHDPr459Ady7s3hQ
823 ms
bKDZm0n2Dms8-vdQuEWKXfAtQlltzRdGjidyrImdK5o
701 ms
small_logo.png
599 ms
main_img_1.jpg
455 ms
p.gif
134 ms
socrata-apps.ttf
524 ms
prIMHwO-dhQ6m5OV5oixxOeSqWf6dssBqfTRS7HLOCwffHAsgsMmeMJ6Mk6f5Mt.woff
36 ms
1Y74MBw4GHAzhUCE_mkrBhdWLOObc360npP7uULMnBMffHcsgsMmeMJ6Mk6f5gI.woff
48 ms
xpZLtTKBTfirWnJM5s4w6B4Azc3vEzndzQD8_qssMbSffHPsgsMmeMJ6Mk6f5Mb.woff
79 ms
C-hOknuf-55iQkbpzJmBdD0xgd-wCewb8EQFHPEuqctff4kQgsMmeMJ6Mk6f5MS.woff
77 ms
collect
29 ms
data.oregon.gov
96 ms
spinner_background.png
262 ms
mixpanel-2.2.min.js
59 ms
9c8s-3c6m.json
282 ms
views.json
407 ms
views.json
580 ms
views.json
571 ms
menu_icons.png
380 ms
UUo6vtDLDshF4IHYdD2mVu_u754Rz-R7GHqv677BIoqff4nygsM-eMJ6Mk6f5Mb.woff
33 ms
paJETsJGbYpSA5KN_3c2rHoYyO0nnhlTcBMSDcaHXq9ff4RygsM-eMJ6Mk6f5Mw.woff
33 ms
oRibSQALMng_d1X07tB5_D6PghlVI2GC9SjF1NZT61Cff4_ygsM-eMJ6Mk6f5MS.woff
31 ms
FLMr8mj1B8mdVybf8eY8QKZyy3_j-DwbfgFNw0zSiIwff4zygsM-eMJ6Mk6f5Mt.woff
35 ms
UDRzq2jDC1YtGwBDz4E3rJVygCKJh_h_CiwXGjaSca9ff4xygsM-eMJ6Mk6f5gI.woff
55 ms
collect
36 ms
snuffleupasnake.gif
381 ms
BrandedSpinner.gif
451 ms
39 ms
print.css
94 ms
data.oregon.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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
[aria-*] attributes are not valid or misspelled
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
data.oregon.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
Missing source maps for large first-party JavaScript
data.oregon.gov SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Data.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 Data.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.
data.oregon.gov
Open Graph description is not detected on the main page of Data 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: