5 sec in total
987 ms
3.8 sec
219 ms
Welcome to bend.or.us homepage info - get ready to check Bend best content for United States right away, or after learning these important things about bend.or.us
The City of Bend serves the community, focusing on core services such as public safety, utilities, economic and community development.
Visit bend.or.usWe analyzed Bend.or.us page load time and found that the first response time was 987 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
bend.or.us performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value12.6 s
0/100
25%
Value6.7 s
36/100
10%
Value980 ms
28/100
30%
Value0.069
96/100
15%
Value11.4 s
19/100
10%
987 ms
142 ms
279 ms
225 ms
154 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 87% of them (91 requests) were addressed to the original Bend.or.us, 3% (3 requests) were made to S.ytimg.com and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Bend.or.us.
Page size can be reduced by 839.9 kB (30%)
2.8 MB
2.0 MB
In fact, the total size of Bend.or.us main page is 2.8 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. 60% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 66.8 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 22.7 kB, which is 27% 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 66.8 kB or 78% of the original size.
Potential reduce by 13.8 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. Bend images are well optimized though.
Potential reduce by 479.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 479.0 kB or 68% of the original size.
Potential reduce by 280.3 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. Bend.or.us needs all CSS files to be minified and compressed as it can save up to 280.3 kB or 83% of the original size.
Number of requests can be reduced by 38 (38%)
100
62
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bend. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
bend.or.us
987 ms
admin.css
142 ms
custom.css
279 ms
editor.css
225 ms
dropdownmegamenu.css
154 ms
fontwitch.js
240 ms
jquery-1.5.2.min.js
412 ms
thickbox.js
239 ms
thickbox.css
321 ms
dropdownmegamenu.js
341 ms
__utm.js
206 ms
FrontEndScripts.js
234 ms
HomeSlideshow.js
182 ms
HomeSlideshow_Code.js
233 ms
homepage_scripts.js
470 ms
sifr.js
116 ms
large.css
75 ms
medium.css
74 ms
small.css
77 ms
x-small.css
74 ms
w.js
14 ms
spacer.gif
87 ms
goBtn.gif
111 ms
button1.png
177 ms
button2.png
150 ms
button3.png
139 ms
button4.png
188 ms
button5.png
208 ms
button6.png
239 ms
body_bg_shadow_home.png
549 ms
footer_strip.gif
260 ms
clickstream.min.js
12 ms
__utm.gif
253 ms
search_bg.png
249 ms
mainnav_bg.gif
269 ms
2_home.png
384 ms
3_home.png
384 ms
4_home.png
385 ms
5_home.png
387 ms
6_home.png
401 ms
7.png
459 ms
home_bottom.png
464 ms
home_left.png
496 ms
puQS1fx02Lo
117 ms
button1_over.png
460 ms
button2_over.png
518 ms
button3_over.png
548 ms
button4_over.png
544 ms
button5_over.png
564 ms
button6_over.png
591 ms
visit_bend.png
603 ms
home_right.png
622 ms
buttons_prev.png
705 ms
buttons_next.png
654 ms
content_strip.png
664 ms
home_left.gif
685 ms
spotlight_title.gif
784 ms
spotlight_bg.gif
749 ms
video_bg.png
772 ms
1.jpg
918 ms
storage.luckyorange.net
39 ms
2.jpg
882 ms
3.jpg
818 ms
settings.luckyorange.net
95 ms
4.jpg
766 ms
www-embed-player-vflZsBgOl.css
59 ms
www-embed-player.js
84 ms
base.js
163 ms
5.jpg
818 ms
6.jpg
765 ms
7.jpg
804 ms
8.jpg
815 ms
9.jpg
821 ms
10.jpg
891 ms
11.jpg
946 ms
error.aspx
540 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
50 ms
ad_status.js
55 ms
12.jpg
794 ms
13.jpg
749 ms
social_bg.png
768 ms
facebook.jpg
996 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
93 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
102 ms
twitter.jpg
1075 ms
youtube.jpg
1000 ms
rss.jpg
1052 ms
email.jpg
966 ms
tab1.png
954 ms
tab2.png
969 ms
news_bg.jpg
964 ms
controls_bg.png
998 ms
prev.gif
994 ms
next.gif
1030 ms
news_more.gif
993 ms
events_bg.jpg
1006 ms
day_divider.png
1013 ms
events_more.gif
1013 ms
footer_bg.png
1062 ms
footer_divider.gif
1001 ms
body_bg7.jpg
1027 ms
loadingAnimation.gif
1033 ms
xx-small.css
75 ms
print.css
74 ms
inspectlet.js
6 ms
bend.or.us 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
Links do not have a discernible name
bend.or.us 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
Missing source maps for large first-party JavaScript
bend.or.us 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bend.or.us can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Bend.or.us 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.
bend.or.us
Open Graph description is not detected on the main page of Bend. 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: