Tools & Wizards About Us
ocedo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ocedo.com

Application Acceleration & Delivery Solutions | Riverbed

Page Load Speed

3.5 sec in total

First Response

258 ms

Resources Loaded

2.8 sec

Page Rendered

437 ms

ocedo.com screenshot

About Website

Click here to check amazing Ocedo content for United States. Otherwise, check out these important facts you probably never knew about ocedo.com

Explore how application acceleration services with Riverbed can help your digital enterprise execute fast, agile and secure app delivery to anyone, anywhere.

Visit ocedo.com

Key Findings

We analyzed Ocedo.com page load time and found that the first response time was 258 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.

Performance Metrics

ocedo.com performance score

0

Network Requests Diagram

ocedo.com

258 ms

152 ms

app.js

404 ms

css

62 ms

css

74 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Ocedo.com, 85% (45 requests) were made to Cdn.ocedo.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Cdn.ocedo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 201.1 kB (6%)

Content Size

3.5 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ocedo.com main page is 3.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. 35% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 53.7 kB

  • Original 71.5 kB
  • After minification 71.3 kB
  • After compression 17.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. 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 53.7 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 6.3 kB

  • Original 3.2 MB
  • After minification 3.2 MB

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. Ocedo images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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.

CSS Optimization

-86%

Potential reduce by 141.1 kB

  • Original 164.0 kB
  • After minification 128.4 kB
  • After compression 22.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. Ocedo.com needs all CSS files to be minified and compressed as it can save up to 141.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (50%)

Requests Now

48

After Optimization

24

  • Images
  • JavaScript
  • CSS

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ocedo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ocedo.com

ocedo.com

258 ms

152 ms

app.js

app.js

404 ms

css

css

62 ms

css

css

74 ms

css

css

87 ms

style.css

style.css

453 ms

logo.png

logo.png

244 ms

main1mob.jpg

main1mob.jpg

263 ms

intro-ico1.png

intro-ico1.png

356 ms

intro-ico2.png

intro-ico2.png

342 ms

intro-ico3.png

intro-ico3.png

373 ms

intro-ico4.png

intro-ico4.png

355 ms

arr-down.png

arr-down.png

449 ms

acquia_marina_logo.png

acquia_marina_logo.png

465 ms

logo-acquifer_1.png

logo-acquifer_1.png

550 ms

logo-fischer.png

logo-fischer.png

563 ms

logo_stockmeier_1.png

logo_stockmeier_1.png

565 ms

icotw.png

icotw.png

566 ms

icofb.png

icofb.png

642 ms

ico-linkedin2.png

ico-linkedin2.png

667 ms

ico-gmail2.png

ico-gmail2.png

752 ms

ico-xing2.png

ico-xing2.png

773 ms

analytics.js

analytics.js

207 ms

icon_menu_a2.png

icon_menu_a2.png

646 ms

contact-phone-home.png

contact-phone-home.png

673 ms

main1.jpg

main1.jpg

745 ms

evt-chevron.png

evt-chevron.png

750 ms

evt-pointer.png

evt-pointer.png

840 ms

ico-pdf.png

ico-pdf.png

888 ms

ico-video.png

ico-video.png

896 ms

footer-arrow3.png

footer-arrow3.png

897 ms

minipop-close.png

minipop-close.png

945 ms

main2.jpg

main2.jpg

974 ms

main3.jpg

main3.jpg

1049 ms

main4.jpg

main4.jpg

1101 ms

main5.jpg

main5.jpg

1133 ms

main6.jpg

main6.jpg

1130 ms

main2mob.jpg

main2mob.jpg

1163 ms

main3mob.jpg

main3mob.jpg

1178 ms

main4mob.jpg

main4mob.jpg

1253 ms

main5mob.jpg

main5mob.jpg

1311 ms

main6mob.jpg

main6mob.jpg

1368 ms

DINRoundWeb.woff

DINRoundWeb.woff

1354 ms

collect

collect

27 ms

DINRoundWeb-Bold.woff

DINRoundWeb-Bold.woff

1259 ms

solutions-pager.png

solutions-pager.png

1264 ms

collect

collect

49 ms

home-pager-active.png

home-pager-active.png

1265 ms

home-pager.png

home-pager.png

1281 ms

solutions-pager-active.png

solutions-pager-active.png

1227 ms

arrow-left-small.png

arrow-left-small.png

202 ms

arrow-right-small.png

arrow-right-small.png

197 ms

SEO Factors

ocedo.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ocedo.com 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 Ocedo.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.

Social Sharing Optimization

ocedo.com

Open Graph description is not detected on the main page of Ocedo. 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: