13.5 sec in total
204 ms
10 sec
3.3 sec
Click here to check amazing Polycom content for Canada. Otherwise, check out these important facts you probably never knew about polycom.ca
Poly is the leader in video and voice solutions. Learn how our technology can help your organization unleash the power of team collaboration.
Visit polycom.caWe analyzed Polycom.ca page load time and found that the first response time was 204 ms and then it took 13.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
polycom.ca performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value54.1 s
0/100
25%
Value37.9 s
0/100
10%
Value56,900 ms
0/100
30%
Value0.001
100/100
15%
Value72.8 s
0/100
10%
204 ms
2151 ms
421 ms
499 ms
391 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Polycom.ca, 26% (39 requests) were made to Poly.scene7.com and 15% (22 requests) were made to Poly.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Poly.scene7.com.
Page size can be reduced by 1.1 MB (15%)
7.5 MB
6.3 MB
In fact, the total size of Polycom.ca main page is 7.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.5 MB which makes up the majority of the site volume.
Potential reduce by 133.5 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 44.1 kB, which is 29% 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 133.5 kB or 87% of the original size.
Potential reduce by 513.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. Polycom images are well optimized though.
Potential reduce by 502.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 502.7 kB or 63% of the original size.
Potential reduce by 5 B
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. Polycom.ca has all CSS files already compressed.
Number of requests can be reduced by 85 (64%)
133
48
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Polycom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
polycom.ca
204 ms
en
2151 ms
lru7xia.css
421 ms
launch-c87681b2d15a.min.js
499 ms
CoveoFullSearch.min.css
391 ms
clientlib-vendor.min.a95832730a93238e21f059ba8be59273.css
306 ms
clientlib-base.min.9bcdeb74a1583493a650232a44196090.css
408 ms
dynamicmedia.min.a97e0418f0d0d6fe2eea57c7dc5e8804.css
302 ms
viewer.min.4618b42d2de5cb16b5ebca7fdf77812d.js
250 ms
jquery.min.1494c0abbe501301e2ab9daecc6082a8.js
302 ms
utils.min.4a192b590a2c2926fb000264370c0588.js
388 ms
dynamicmedia.min.738776da43320f8d780014c241ca78a5.js
378 ms
i18n.min.68da31d5bd4fb4fe82646d5b80611425.js
480 ms
clientlib-vendor.min.ecac9a8a95cb537f891d78ee206be390.js
424 ms
container.min.c93c66543169d874d70f480f22d0e35f.js
393 ms
clientlib-base.min.5f0233d4f3e937c8854bbacb749e78b1.js
433 ms
CoveoJsSearch.Lazy.min.js
432 ms
templates.js
398 ms
p.css
121 ms
css
1146 ms
poly-logo.svg
707 ms
poly-voyager-focus-2-hero-high-res-rgb
3929 ms
poly-name-white.svg
686 ms
voyager-4320-hero-high-res-rgb
4335 ms
trio_c60_top_print_rgb
4313 ms
poly-sync-20-top-hero-scaled
4309 ms
ccx-600-family-bundle-opensip-front-screen
4308 ms
vvx-450-microban-front
4310 ms
poly-studio-p5-hero-high-res-rgb
4310 ms
poly_G7500_Studio-E70_TC8_web
4333 ms
papa-lens-hero
4328 ms
clariti-laptop-image
4337 ms
poly-plus-hero-sqaure-small
4326 ms
poly-studio-p21-left-hero-high-res-rgb
4334 ms
Studio%20X70%20Left_TC8_Poly_print_rgb
4328 ms
large-room-kit-mtrow-1
4331 ms
front-View-composite-monitor-not-included
4335 ms
realpresence-utility-cart-500-2
4421 ms
id
2890 ms
fbevents.js
2138 ms
uwt.js
3504 ms
notice
3485 ms
qualified.js
3395 ms
bg-color-burst
3731 ms
studio-e70-room-2.jpg
3709 ms
d
1831 ms
d
2772 ms
d
2771 ms
d
2564 ms
d
2769 ms
d
2772 ms
d
2771 ms
d
3287 ms
d
3287 ms
d
3286 ms
webicon-twitter-circle.svg
1771 ms
webicon-facebook-circle.svg
1761 ms
webicon-youtube-circle.svg
1744 ms
webicon-linkedin-circle.svg
1810 ms
webicon-instagram-circle.svg
1811 ms
POLY_logo_lava-white.png
2741 ms
location.svg
2740 ms
all-together-photo-far-end-options
3021 ms
buy-more-bucket
3234 ms
RC2ef965a9914740e889b0db4b0311f568-source.min.js
1503 ms
RCd3f0c617f51244cfa238d3836fb83828-source.min.js
1930 ms
RC08a6ed7528cb40b595345038227fc62e-source.min.js
1929 ms
RCe1e92f46414149e598b1e9eb865ca0d0-source.min.js
1929 ms
BasicZoomViewer.js
2077 ms
FlyoutViewer.js
2074 ms
MixedMediaViewer.js
2075 ms
SpinViewer.js
2153 ms
VideoViewer.js
2150 ms
ZoomViewer.js
2148 ms
ZoomVerticalViewer.js
2132 ms
responsive_image.js
2120 ms
identity.js
702 ms
824092847925969
1177 ms
dest5.html
1159 ms
log
467 ms
v1.7-9751
450 ms
siteanalyze_75220.js
321 ms
js
172 ms
ibs:dpid=411&dpuuid=Yz2a_QAAADdL8wOj
117 ms
notice
123 ms
js
95 ms
js
125 ms
headset-icon-white
156 ms
bannermsg
197 ms
desk-phone-icon-white
302 ms
conference-phone-icon-white
302 ms
video-conferencing-icon-white
193 ms
software-icon-white
300 ms
services-icon-white
298 ms
poly-r30-left-high-res-rgb
681 ms
poly-edge-e500-series-hero-high-res-rgb-1
353 ms
2.0-lower-op-costs-2x
445 ms
poly-plus-hero-sqaure-small
411 ms
microsft-certified-teams-badge-grey-500x138
375 ms
zoom_certified_wide
350 ms
analytics.js
59 ms
image.aspx
148 ms
js
101 ms
collect
72 ms
collect
66 ms
conversion_async.js
60 ms
up_loader.1.1.0.js
26 ms
poly.jsp
37 ms
72 ms
37 ms
RC29f124f0eebd4cd6bbc1bba508ba98b2-source.min.js
69 ms
RC29aeba80963d4fe893e9f8b1c3f01d4f-source.min.js
62 ms
munchkin.js
143 ms
RC9d846d753a28499c9366d7158e509760-source.min.js
60 ms
bat.js
188 ms
RC49826797144c470e990dbe4e94c83be2-source.min.js
52 ms
insight.min.js
177 ms
js
56 ms
js
128 ms
js
160 ms
adsct
277 ms
adsct
276 ms
ae.js
193 ms
up
173 ms
247 ms
activityi;src=9151563;type=globa0;cat=newco0;ord=8420820387872;gtm=2oda30;auiddc=591584134.1664981754;u1=https%3A%2F%2Fwww.poly.com%2Fus%2Fen%3Furc%3D;~oref=https%3A%2F%2Fwww.poly.com%2Fus%2Fen%3Furc%3D
265 ms
dtag.js
176 ms
munchkin.js
81 ms
25004750.js
99 ms
284 ms
visitWebPage
555 ms
visitWebPage
634 ms
bootstrap.js
307 ms
PolyfillsModule.js
329 ms
25004750
405 ms
poly-utm.js
583 ms
src=9151563;type=globa0;cat=newco0;ord=8420820387872;gtm=2oda30;auiddc=*;u1=https%3A%2F%2Fwww.poly.com%2Fus%2Fen%3Furc%3D;~oref=https%3A%2F%2Fwww.poly.com%2Fus%2Fen%3Furc%3D
321 ms
universal_pixel.1.1.0.js
141 ms
11.49f0b3e462d2d1363ad2.chunk.js
96 ms
clarity.js
57 ms
Targeting.php
275 ms
rubicon
15 ms
27 ms
appnexus
15 ms
poly-utm-tracker.min.js
138 ms
fullcircle.js
36 ms
27 ms
c.gif
45 ms
polycom.ca accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
polycom.ca 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
polycom.ca 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
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
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 Polycom.ca 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 Polycom.ca 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.
polycom.ca
Open Graph data is detected on the main page of Polycom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: