1.1 sec in total
77 ms
856 ms
175 ms
Click here to check amazing WOBI Live content. Otherwise, check out these important facts you probably never knew about wobilive.com
WOBI is a powerhouse of actionable ideas from people shaping the business world: Events; TV; Print Media; WOBI.com
Visit wobilive.comWe analyzed Wobilive.com page load time and found that the first response time was 77 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
wobilive.com performance score
77 ms
82 ms
33 ms
36 ms
35 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wobilive.com, 44% (43 requests) were made to Cdn.aws.wobi.com and 12% (12 requests) were made to Wobi.com. The less responsive or slowest element that took the longest time to load (169 ms) relates to the external source Trk.etrigue.com.
Page size can be reduced by 1.1 MB (67%)
1.6 MB
546.8 kB
In fact, the total size of Wobilive.com main page is 1.6 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. 70% of websites need less resources to load. Javascripts take 954.0 kB which makes up the majority of the site volume.
Potential reduce by 75.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 75.2 kB or 74% of the original size.
Potential reduce by 91.1 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. Obviously, WOBI Live needs image optimization as it can save up to 91.1 kB or 45% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 606.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 606.4 kB or 64% of the original size.
Potential reduce by 325.6 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. Wobilive.com needs all CSS files to be minified and compressed as it can save up to 325.6 kB or 84% of the original size.
Number of requests can be reduced by 60 (67%)
89
29
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WOBI Live. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
wobilive.com
77 ms
www.wobi.com
82 ms
google_service.js
33 ms
iMAWebCookie.js
36 ms
css
35 ms
cdn_css_119fbcfa9ccbec2281de17459534eea4.css
32 ms
jquery.min.js
28 ms
drupal.js
28 ms
ajax_load.js
14 ms
ui.core.min.js
27 ms
ui.dialog.min.js
29 ms
ui.draggable.min.js
30 ms
parent.js
32 ms
automodal.js
32 ms
fivestar.js
32 ms
googleanalytics.js
30 ms
jquery.aop.js
32 ms
lightbox_video.js
33 ms
lightbox.js
35 ms
uc_roles.js
37 ms
jquery.cycle.all.min.js
36 ms
views_slideshow.js
36 ms
script.js
37 ms
jquery.infieldlabel.js
38 ms
geoip.js
38 ms
homepage.js
39 ms
jquery.ba-hashchange.min.js
47 ms
script.js
48 ms
jquery.a_form.packed.js
47 ms
ajax.js
46 ms
wbf_modal_one_time.js
53 ms
html5placeholder.jquery.js
51 ms
script.js
103 ms
PIE.js
55 ms
jquery.cookie.js
106 ms
wbf_twitter_profiles.js
103 ms
wbf_watchdog.js
106 ms
addthis_widget.js
33 ms
jsapi
45 ms
conversion.js
50 ms
google_ads.js
34 ms
etriguelive.js
169 ms
prum.min.js
48 ms
ads
48 ms
palette.png
19 ms
poweredbyHSM.jpg
18 ms
bg-false-cover.png
18 ms
logo-wobi-transparent.png
22 ms
en.png
19 ms
es.png
19 ms
it.png
18 ms
bg-sidebar-top.png
58 ms
13 ms
default+en.css
8 ms
default.css
23 ms
default+en.I.js
25 ms
track.php
127 ms
default.css
31 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
23 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
26 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
28 ms
icon-arrow-black.gif
23 ms
refineFilterIcons.gif
20 ms
ads
33 ms
1416777457558304662
32 ms
ads
47 ms
osd.js
20 ms
1791450681195809135
8 ms
social-facebook-logo.25.png
11 ms
social-twitter.25.png
10 ms
8712.js
124 ms
dc.js
53 ms
300lo.json
41 ms
menu.c646c958f7e380f4e000.js
36 ms
90 ms
0.png
55 ms
1.png
53 ms
2.png
53 ms
3.png
55 ms
4.png
54 ms
5.png
56 ms
6.png
56 ms
7.png
57 ms
palette_disable.png
56 ms
sh.8e5f85691f9aaa082472a194.html
47 ms
__utm.gif
37 ms
37 ms
red_pjson
21 ms
seg
66 ms
async-ads.js
51 ms
bg-form-elements.gif
17 ms
t.js
34 ms
google_custom_search_watermark.gif
27 ms
small-logo.png
29 ms
search_box_icon.png
27 ms
clear.png
29 ms
beacon.gif
33 ms
wobilive.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wobilive.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 Wobilive.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.
wobilive.com
Open Graph description is not detected on the main page of WOBI Live. 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: