1.9 sec in total
217 ms
1.5 sec
204 ms
Click here to check amazing Lifesize content for Colombia. Otherwise, check out these important facts you probably never knew about lifesize.com
Elevate your business communications with our flexible solutions and discover the future of corporate communication with our comprehensive suite of enterprise video solutions.
Visit lifesize.comWe analyzed Lifesize.com page load time and found that the first response time was 217 ms and then it took 1.7 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.
lifesize.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value10.9 s
0/100
25%
Value5.4 s
57/100
10%
Value1,410 ms
15/100
30%
Value1.156
1/100
15%
Value12.6 s
14/100
10%
217 ms
422 ms
75 ms
45 ms
61 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lifesize.com, 58% (48 requests) were made to Enghousevideo.com and 34% (28 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (452 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 400.7 kB (50%)
803.9 kB
403.2 kB
In fact, the total size of Lifesize.com main page is 803.9 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. 75% 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. HTML takes 444.7 kB which makes up the majority of the site volume.
Potential reduce by 393.2 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 393.2 kB or 88% 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. Lifesize images are well optimized though.
Potential reduce by 364 B
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 7.2 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. Lifesize.com needs all CSS files to be minified and compressed as it can save up to 7.2 kB or 12% of the original size.
Number of requests can be reduced by 44 (86%)
51
7
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifesize. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
lifesize.com
217 ms
lifesize
422 ms
autoptimize_single_704872731ae4e91e1d52d1e3fcdfe68e.css
75 ms
autoptimize_single_688d360e90d71fd1a201875aeb635ad6.css
45 ms
autoptimize_single_54b21ff9a1517fe870ec5c5b5909c5a8.css
61 ms
autoptimize_single_9389a240ec2d748902e2f3d837d46912.css
59 ms
autoptimize_single_f733d0fb45713b13b3ef2e60abf101ba.css
36 ms
autoptimize_single_f9d429183da3884029ca2bdf7dac6e59.css
49 ms
autoptimize_single_b659a7ae2f6b8d4222586bca8f965e98.css
71 ms
front.min.css
72 ms
style.min.css
87 ms
style.min.css
79 ms
upw-theme-standard.min.css
71 ms
style.min.css
76 ms
autoptimize_single_ef2268cdc0b5313c8794c32d6d3222e9.css
90 ms
jquery.min.js
97 ms
jquery-migrate.min.js
108 ms
jquery.fitvids.min.js
115 ms
frontend.min.js
110 ms
autoptimize_single_b213c523f289556b68d89b026fdcfa37.js
111 ms
ie-compat.min.js
111 ms
jquery.cookie.min.js
32 ms
autoptimize_single_948adbc4b2fd9cd368d5c90e039dbf20.js
117 ms
et-core-unified-228566.min.css
64 ms
lazysizes.min.js
66 ms
mediaelementplayer-legacy.min.css
106 ms
wp-mediaelement.min.css
106 ms
front.min.js
107 ms
scripts.min.js
112 ms
autoptimize_single_fa07f10043b891dacdb82f26fd2b42bc.js
122 ms
autoptimize_single_00346ced8d8b5c664b826381bdcd7c48.js
110 ms
autoptimize_single_bf7fe805ab945e4b2c4d56da59476811.js
111 ms
frontend-bundle.min.js
110 ms
frontend-bundle.min.js
111 ms
frontend-bundle.min.js
137 ms
autoptimize_single_20b3b806e556954dbacaf87d635d399d.js
143 ms
app.min.js
131 ms
autoptimize_single_d71b75b2327258b1d01d50590c1f67ca.js
122 ms
autoptimize_single_7e5dcbf354f375199044871380a9485c.js
129 ms
mediaelement-and-player.min.js
154 ms
mediaelement-migrate.min.js
147 ms
wp-mediaelement.min.js
148 ms
autoptimize_single_aeec463b37d075ea9b5ed5cd4ea88fa7.js
241 ms
gtm.js
111 ms
et-divi-dynamic-tb-43985-tb-228625-228566-late.css
61 ms
EV-stacked-color_trimmed.svg
85 ms
en_US.png
84 ms
fr_FR.png
85 ms
Enghouse-lifesize-icon-white.png
149 ms
S6uyw4BMUTPHjxAwWA.woff
264 ms
S6uyw4BMUTPHjxAwWw.ttf
296 ms
S6u9w4BMUTPHh7USSwaPHw.woff
295 ms
S6u9w4BMUTPHh7USSwaPHA.ttf
295 ms
S6u8w4BMUTPHh30AUi-s.woff
295 ms
S6u8w4BMUTPHh30AUi-v.ttf
294 ms
S6u9w4BMUTPHh6UVSwaPHw.woff
293 ms
S6u9w4BMUTPHh6UVSwaPHA.ttf
336 ms
S6u9w4BMUTPHh50XSwaPHw.woff
295 ms
S6u9w4BMUTPHh50XSwaPHA.ttf
296 ms
modules.woff
261 ms
modules.woff
294 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
333 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
295 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
294 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
334 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
336 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
336 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff
336 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
448 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff
448 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
450 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
450 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
450 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
449 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
452 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
452 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
451 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff
449 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
452 ms
script.js
377 ms
js
244 ms
destination
355 ms
landing
333 ms
lifesize.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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
lifesize.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
lifesize.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 Lifesize.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 Lifesize.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.
lifesize.com
Open Graph data is detected on the main page of Lifesize. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: