2.7 sec in total
174 ms
1.5 sec
1 sec
Click here to check amazing Oregon River content for United States. Otherwise, check out these important facts you probably never knew about oregonriver.com
10 Oregon river rafting trips. Clackamas River 1/2 & Full Day, & 5 others. Multiday rafting on the Rogue River, Lower Salmon River & 3 others.
Visit oregonriver.comWe analyzed Oregonriver.com page load time and found that the first response time was 174 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
oregonriver.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value13.2 s
0/100
25%
Value10.3 s
8/100
10%
Value1,580 ms
12/100
30%
Value0.141
78/100
15%
Value27.8 s
0/100
10%
174 ms
394 ms
24 ms
28 ms
28 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 50% of them (75 requests) were addressed to the original Oregonriver.com, 34% (51 requests) were made to Fonts.gstatic.com and 5% (8 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (518 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 219.8 kB (4%)
5.3 MB
5.1 MB
In fact, the total size of Oregonriver.com main page is 5.3 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 4.1 MB which makes up the majority of the site volume.
Potential reduce by 212.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 212.7 kB or 79% of the original size.
Potential reduce by 0 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. Oregon River images are well optimized though.
Potential reduce by 4.7 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.4 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. Oregonriver.com has all CSS files already compressed.
Number of requests can be reduced by 70 (74%)
94
24
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oregon River. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
oregonriver.com
174 ms
oregonriver.com
394 ms
elementor-icons.min.css
24 ms
frontend-lite.min.css
28 ms
swiper.min.css
28 ms
post-6.css
25 ms
frontend-lite.min.css
32 ms
global.css
39 ms
post-273.css
47 ms
style.min.css
40 ms
theme.min.css
41 ms
header-footer.min.css
50 ms
post-45.css
53 ms
post-70.css
52 ms
text-animations.min.css
57 ms
frontend.min.css
70 ms
all.min.css
87 ms
wprevpro_w3.css
89 ms
style.css
67 ms
css
38 ms
fontawesome.min.css
91 ms
solid.min.css
96 ms
brands.min.css
96 ms
jquery.min.js
102 ms
jquery-migrate.min.js
95 ms
wprs-slick.min.js
95 ms
wprev-public.min.js
95 ms
css2
53 ms
css2
63 ms
owl.carousel.min.js
29 ms
owl.carousel.min.css
40 ms
owl.theme.default.min.css
46 ms
widget-mega-menu.min.css
126 ms
widget-icon-box.min.css
126 ms
widget-loop-builder.min.css
126 ms
widget-icon-list.min.css
126 ms
widget-carousel.min.css
72 ms
animations.min.css
72 ms
particles.js
73 ms
jarallax.min.js
74 ms
parallax.min.js
72 ms
hello-frontend.min.js
73 ms
api.js
71 ms
imagesloaded.min.js
75 ms
webpack-pro.runtime.min.js
79 ms
webpack.runtime.min.js
77 ms
frontend-modules.min.js
78 ms
wp-polyfill-inert.min.js
79 ms
regenerator-runtime.min.js
83 ms
wp-polyfill.min.js
88 ms
hooks.min.js
89 ms
i18n.min.js
186 ms
frontend.min.js
186 ms
waypoints.min.js
186 ms
core.min.js
186 ms
frontend.min.js
185 ms
elements-handlers.min.js
186 ms
frontend.min.js
186 ms
modal-popups.min.js
183 ms
widget_button.js
23 ms
widget_button.css
25 ms
checkout.js
240 ms
gtm.js
241 ms
embed
162 ms
recaptcha__en.js
191 ms
ORE-Logo-BadgeText-1024x327-1.png
152 ms
guided-whitewater-rafting-trips-upper-clackamas.jpg
152 ms
deschutes-multi-day-rafting-bend.jpg
151 ms
hiking-support-thumb-min.jpg
152 ms
oregon-hero-image-min-scaled.jpg
181 ms
ore-swizzle.svg
146 ms
deshutes-rafting-day-trip.jpg
166 ms
rogue-river-rafting-multi-day-trip.jpg
182 ms
listing-image-1-min.jpg
163 ms
listing-image-2-min.jpg
181 ms
listing-image-3-min.jpg
181 ms
ore-rafting-divider-min-scaled.jpg
270 ms
ore-waves.svg
244 ms
reviews-bg-ore-min-scaled.jpg
268 ms
Vector.svg
186 ms
clackamakas-tall-thumb-min.jpg
186 ms
deschutes-tall-thumb-min.jpg
186 ms
rogue-tall-thumb-min.jpg
302 ms
ore-home-footer.png
326 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjQ.ttf
128 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf
163 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf
182 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfAZ9hjQ.ttf
185 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeAZ9hjQ.ttf
184 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjQ.ttf
185 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYAZ9hjQ.ttf
183 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYAZ9hjQ.ttf
181 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYAZ9hjQ.ttf
186 ms
fa-brands-400.woff
129 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHlsZYYvGQ.ttf
333 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHlsZYYfHl-S.ttf
241 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHlsAoYvGQ.ttf
344 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHlsAoYfHl-S.ttf
333 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHlsXIYvGQ.ttf
334 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHlsXIYfHl-S.ttf
240 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHlssIEvGQ.ttf
241 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHlssIEfHl-S.ttf
334 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHlsgoEvGQ.ttf
336 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHlsgoEfHl-S.ttf
333 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHls3IEvGQ.ttf
433 ms
XLY4IZPxYpJfTbZAFXWzNT2SO8wpWHls3IEfHl-S.ttf
341 ms
gNMbW3NwSYq_9WD34ngK5F8vR8T0PVxx8StPaWQ.ttf
334 ms
gNMbW3NwSYq_9WD34ngK5F8vR8T0PVxD8StPaWQ.ttf
334 ms
gNMbW3NwSYq_9WD34ngK5F8vR8T0PVwv8StPaWQ.ttf
334 ms
gNMbW3NwSYq_9WD34ngK5F8vR8T0PVzx8StPaWQ.ttf
334 ms
gNMbW3NwSYq_9WD34ngK5F8vR8T0PVxx8CtPaWQ.ttf
336 ms
gNMbW3NwSYq_9WD34ngK5F8vR8T0PVyv9itPaWQ.ttf
336 ms
gNMbW3NwSYq_9WD34ngK5F8vR8T0PVyW9itPaWQ.ttf
336 ms
fa-solid-900.woff
178 ms
fa-regular-400.woff
339 ms
845CNN4-AJyIGvIou-6yJKyptyOpOcr_.ttf
337 ms
845CNN4-AJyIGvIou-6yJKyptyOpOfr4DG0.ttf
336 ms
XLY2IZPxYpJfTbZAFV-6B8JKUqez9n55SsIgXW-VU8o.ttf
336 ms
XLY2IZPxYpJfTbZAFV-6B8JKUqez9n55SsJHXW-VU8o.ttf
467 ms
XLY2IZPxYpJfTbZAFV-6B8JKUqez9n55SsIZXW-VU8o.ttf
337 ms
XLY2IZPxYpJfTbZAFV-6B8JKUqez9n55SsL1Wm-VU8o.ttf
345 ms
XLY2IZPxYpJfTbZAFV-6B8JKUqez9n55SsLHWm-VU8o.ttf
338 ms
XLY2IZPxYpJfTbZAFV-6B8JKUqez9n55SsKZWm-VU8o.ttf
518 ms
eicons.woff
465 ms
rs=ABjfnFX56za78Ybjhjtsbp5AK7-r7MbSqg
99 ms
css
39 ms
js
180 ms
m=gmeviewer_base
120 ms
anchor
84 ms
SlGVmQieoJcKemNeeY4hkHNSaA.ttf
215 ms
SlGQmQieoJcKemNecTUEgA.ttf
165 ms
styles__ltr.css
113 ms
recaptcha__en.js
115 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
162 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
162 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
162 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
161 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
162 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
160 ms
lazy.min.js
107 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
107 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
106 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
106 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
142 ms
PSKopaksc4v0TeE9MSufUBd6uLsTLN3_1JKIESb4JYg.js
150 ms
webworker.js
149 ms
logo_48.png
138 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
22 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
21 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
22 ms
recaptcha__en.js
65 ms
oregonriver.com 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
oregonriver.com 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
oregonriver.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oregonriver.com 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 Oregonriver.com 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.
oregonriver.com
Open Graph data is detected on the main page of Oregon River. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: