Tools & Wizards About Us
obihai.com screenshot

Report Summary

  • 0

    Performance

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

obihai.com

Poly | Video & Voice Collaboration Solutions | HP® Official Site

Page Load Speed

2 sec in total

First Response

187 ms

Resources Loaded

1.6 sec

Page Rendered

200 ms

obihai.com screenshot

About Website

Visit obihai.com now to see the best up-to-date Obihai content for United States and also check out these interesting facts you probably never knew about obihai.com

Poly, formerly Plantronics & Polycom, is now an HP brand. Learn how HP and Poly collaboration solutions can create more meaningful meetings for your workforce.

Visit obihai.com

Key Findings

We analyzed Obihai.com page load time and found that the first response time was 187 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

obihai.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

1/100

10%

LCP (Largest Contentful Paint)

Value33.1 s

0/100

25%

SI (Speed Index)

Value21.0 s

0/100

10%

TBT (Total Blocking Time)

Value8,640 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.997

2/100

15%

TTI (Time to Interactive)

Value44.7 s

0/100

10%

Network Requests Diagram

www.obihai.com

187 ms

acss.min.css

81 ms

tweet_button.1380844203.html

134 ms

jquery-1.11.0.min.js

227 ms

googleanalytics.min.js

140 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 55% of them (22 requests) were addressed to the original Obihai.com, 18% (7 requests) were made to Apis.google.com and 5% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (546 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.7 kB (21%)

Content Size

557.3 kB

After Optimization

437.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Obihai.com main page is 557.3 kB. 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 368.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 13.7 kB

  • Original 19.0 kB
  • After minification 18.7 kB
  • After compression 5.3 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 13.7 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 32 B

  • Original 368.9 kB
  • After minification 368.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. Obihai images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 69.5 kB

  • Original 124.8 kB
  • After minification 124.8 kB
  • After compression 55.4 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 69.5 kB or 56% of the original size.

CSS Optimization

-82%

Potential reduce by 36.5 kB

  • Original 44.6 kB
  • After minification 44.6 kB
  • After compression 8.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. Obihai.com needs all CSS files to be minified and compressed as it can save up to 36.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (36%)

Requests Now

39

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.obihai.com

www.obihai.com

187 ms

acss.min.css

acss.min.css

81 ms

tweet_button.1380844203.html

tweet_button.1380844203.html

134 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

227 ms

googleanalytics.min.js

googleanalytics.min.js

140 ms

topmenu.min.js

topmenu.min.js

171 ms

frontpagerotate.min.js

frontpagerotate.min.js

170 ms

widgets.js

widgets.js

199 ms

platform.js

platform.js

90 ms

logo.png

logo.png

168 ms

wtriangle.min.svg

wtriangle.min.svg

169 ms

OBiTalk-si.png

OBiTalk-si.png

204 ms

slide1_nogv_200.jpg

slide1_nogv_200.jpg

391 ms

198x326-sp2.jpg

198x326-sp2.jpg

368 ms

obi500vs_nodeal.png

obi500vs_nodeal.png

447 ms

anveo_logo_wide_202x60.png

anveo_logo_wide_202x60.png

285 ms

PhonePower_web_202_60.jpg

PhonePower_web_202_60.jpg

284 ms

obi-setup.png

obi-setup.png

300 ms

voxie-sm.png

voxie-sm.png

340 ms

5-stars1.png

5-stars1.png

366 ms

mail-link.png

mail-link.png

381 ms

jot

jot

145 ms

like.php

like.php

286 ms

ga.js

ga.js

42 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

64 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

88 ms

fastbutton

fastbutton

155 ms

__utm.gif

__utm.gif

45 ms

postmessageRelay

postmessageRelay

42 ms

api.js

api.js

109 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

76 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

64 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

31 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

45 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

481 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

546 ms

slide2_508.jpg

slide2_508.jpg

223 ms

slide3.jpg

slide3.jpg

238 ms

198x326-byod4.jpg

198x326-byod4.jpg

134 ms

198x326-bob2.jpg

198x326-bob2.jpg

134 ms

Accessibility Review

obihai.com accessibility score

89

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

obihai.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

obihai.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

obihai.com

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