4.9 sec in total
144 ms
3.9 sec
916 ms
Visit mobile.obeo.com now to see the best up-to-date Mobile OBEO content for United States and also check out these interesting facts you probably never knew about mobile.obeo.com
Obeo
Visit mobile.obeo.comWe analyzed Mobile.obeo.com page load time and found that the first response time was 144 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
mobile.obeo.com performance score
144 ms
362 ms
58 ms
99 ms
97 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mobile.obeo.com, 53% (60 requests) were made to Obeo.com and 7% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Player.vimeo.com.
Page size can be reduced by 1.4 MB (25%)
5.7 MB
4.3 MB
In fact, the total size of Mobile.obeo.com main page is 5.7 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 3.9 MB which makes up the majority of the site volume.
Potential reduce by 51.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. This page needs HTML code to be minified as it can gain 15.5 kB, which is 25% 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 51.2 kB or 84% of the original size.
Potential reduce by 133.9 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. Mobile OBEO images are well optimized though.
Potential reduce by 759.8 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 759.8 kB or 69% of the original size.
Potential reduce by 467.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. Mobile.obeo.com needs all CSS files to be minified and compressed as it can save up to 467.6 kB or 83% of the original size.
Number of requests can be reduced by 47 (50%)
94
47
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile OBEO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
mobile.obeo.com
144 ms
www.obeo.com
362 ms
analytics.js
58 ms
jquery.min.js
99 ms
jquery.cookie.min.js
97 ms
bootstrap.min.js
83 ms
slider.css
27 ms
slick.css
32 ms
font-awesome.min.css
30 ms
ftg.css
28 ms
font-awesome.css
32 ms
style.css
29 ms
bootstrap.css
48 ms
custom.css
52 ms
bootstrap-theme.css
46 ms
responsive.css
34 ms
style.css
51 ms
dashicons.min.css
51 ms
jquery.js
72 ms
jquery-migrate.min.js
59 ms
jquery.finalTilesGallery.js
62 ms
jquery.js
296 ms
main.js
60 ms
buttons.js
31 ms
c6803fcd99fed45bbe4c4b79688ec3e4.js
76 ms
navigation.js
13 ms
skip-link-focus-fix.js
13 ms
app.js
12 ms
bootstrap.min.js
13 ms
hoverIntent.min.js
12 ms
maxmegamenu.js
14 ms
slick.js
19 ms
css
23 ms
solution.css
11 ms
collect
49 ms
collect
65 ms
jquery.js
235 ms
Error.aspx
118 ms
ObeoLogo.png
209 ms
147333498
2582 ms
Obeo_SMD%201x8.png
187 ms
slide-7.jpg
192 ms
hero-button-arrow-white.png
189 ms
slide-2.jpg
194 ms
slide-6.jpg
194 ms
house.png
186 ms
camera.png
187 ms
video.png
187 ms
twilight.png
188 ms
elevated.png
189 ms
panorama.png
189 ms
website.png
195 ms
staging.png
191 ms
ObeoUnlimitedLogo.png
189 ms
web-viewer-spw1e.png
197 ms
web-viewer-virtualtour2.png
193 ms
web-viewer-homesite2.png
195 ms
ou_panel_free.png
193 ms
ou_panel_agent.png
194 ms
ou_panel_broker.png
222 ms
ou_panel_enterprise.png
195 ms
gr-pro-photos.png
224 ms
gr-hdr2.png
225 ms
gr-twilight.png
389 ms
gr-elevatedphotography.png
390 ms
bg-panoramic3.jpg
224 ms
gr-virtualtwilight.png
396 ms
gr-customdomains.png
388 ms
gr-virtualstaging.png
393 ms
gr-styledesigner.png
388 ms
logos-left-side2.jpg
392 ms
logos-right-side.jpg
389 ms
ajax-loader.gif
150 ms
arrow-left-white.png
313 ms
getAllAppDefault.esi
228 ms
widget_v2.132.js
42 ms
gray-arrow-left.png
209 ms
gray-arrow-right.png
210 ms
arrow-right-white.png
220 ms
111805548
213 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
182 ms
b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf
183 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
190 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
191 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
192 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
192 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
191 ms
4cKlrioa77J2iqTqBgkRWg.ttf
190 ms
FPdR3EdxH8V9FHdR3EVxF8VdFHdRqmrImBHjh4+eMHbk3xoQhjkAAAFTtF6HAAA=
11 ms
slick.woff
10 ms
player.js
201 ms
player.css
169 ms
ga.js
179 ms
vuid.min.js
162 ms
getSegment.php
203 ms
checkOAuth.esi
102 ms
__utm.gif
45 ms
proxy.html
27 ms
t.dhj
43 ms
t.dhj
30 ms
cm
28 ms
s-3271.xgi
9 ms
hbpix
28 ms
6 ms
7 ms
xrefid.xgi
7 ms
pixel
27 ms
pixel
20 ms
2981
29 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
43 ms
buttons.ab966a004186897711de4a5ed256c924.css
35 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
3 ms
st.1188278743c14064d5e8ae56c8ada29c.js
6 ms
aL63HcygAAVYuCCsAAA==
1 ms
mobile.obeo.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.obeo.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 Mobile.obeo.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.
mobile.obeo.com
Open Graph data is detected on the main page of Mobile OBEO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: