3.6 sec in total
269 ms
3.1 sec
220 ms
Welcome to openbex.com homepage info - get ready to check Openbex best content right away, or after learning these important things about openbex.com
Purchase, sale and lease office spaces, retail units, exclusive buildings, land, plots and retail warehouses in Madrid, Barcelona, Sevilla…
Visit openbex.comWe analyzed Openbex.com page load time and found that the first response time was 269 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
openbex.com performance score
269 ms
237 ms
487 ms
57 ms
539 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 80% of them (53 requests) were addressed to the original Openbex.com, 8% (5 requests) were made to Maps.google.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (563 ms) belongs to the original domain Openbex.com.
Page size can be reduced by 332.9 kB (62%)
536.5 kB
203.6 kB
In fact, the total size of Openbex.com main page is 536.5 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. 45% of websites need less resources to load. Javascripts take 417.9 kB which makes up the majority of the site volume.
Potential reduce by 39.9 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 7.4 kB, which is 14% 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 39.9 kB or 78% of the original size.
Potential reduce by 22.3 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, Openbex needs image optimization as it can save up to 22.3 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 270.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 270.7 kB or 65% of the original size.
Number of requests can be reduced by 42 (68%)
62
20
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Openbex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
openbex.com
269 ms
www.openbex.com
237 ms
487 ms
gtm.js
57 ms
__v_635793816399508355__Core.js
539 ms
__v_635793816399858355__Resources.js
160 ms
__v_635793816399528355__Resources.en-GB.js
158 ms
__v_635793816400488355__jquery.UI.css
237 ms
__v_635793816400508355__Layout.css
311 ms
__v_635793816400348355__HomeOpenbex.css
222 ms
__v_635793816400258355__Common.css
234 ms
__v_635793816400998355__Template.css
310 ms
__v_635793816401228355__Template.Narrow.css
298 ms
__v_635793816399968355__Autocomplete.css
312 ms
__v_635793816399878355__AsyncUpload.css
312 ms
__v_635793816397868355__css_browser_selector.js
372 ms
__v_635793816397298355__NewHome.js
385 ms
__v_635793816400438355__HomePage.css
388 ms
__v_635793816396878355__Home.js
389 ms
js
93 ms
__v_635793816396938355__Marketplace_Properties.js
386 ms
conversion_async.js
24 ms
WebResource.axd
383 ms
ScriptResource.axd
400 ms
ScriptResource.axd
563 ms
ScriptResource.axd
405 ms
32 ms
37 ms
__v_635793816398898355__jquery.numeric.js
331 ms
__v_635793816398898355__jquery.numberformatter-1.2.js
390 ms
__v_635793816398818355__jquery.numberFormatter.js
457 ms
__v_635793816399048355__jquery.templating.js
457 ms
__v_635793816398808355__jquery.maskedinput-1.2.2.js
458 ms
__v_635793816396708355__Helpers.js
466 ms
__v_635793816396348355__Analytics.Production.js
466 ms
__v_635793816395938355__Core.js
483 ms
__v_635793816393748355__Main.js
486 ms
ICON_ENCABEZADO_MODULO_CENTRAL_REPOSO.png
116 ms
transparente.png
117 ms
ICON_ENCABEZADO_MODULO_DCHO_REPOSO.png
116 ms
loading_icon.gif
162 ms
px.gif
161 ms
ico_twitter.png
162 ms
ico_linkedin.png
193 ms
ScriptResource.axd
145 ms
ico_sobre_reposo.png
135 ms
LOGO_OBX_Bbx.png
164 ms
menu_bg.jpg
164 ms
ico_anuncio_reposo.png
160 ms
IMG_FONDO_CAJA_PPAL.jpg
194 ms
buttons_new_searcher.png
199 ms
buttons_op_new_searcher.png
201 ms
ICON_SOBRE_MODULO_CENTRAL_REPOSO.png
240 ms
ICON_REGISTRO_MODULO_DCHO_REPOSO.png
244 ms
footer.png
226 ms
boton_aceptar_reposo.png
264 ms
ga.js
30 ms
common.js
38 ms
util.js
62 ms
controls.js
61 ms
places_impl.js
61 ms
CheckNotification
236 ms
ui-bg_flat_75_ffffff_40x100.png
225 ms
__utm.gif
27 ms
powered-by-google-on-white3.png
38 ms
autocomplete-icons.png
32 ms
openbex.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Openbex.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Openbex.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.
openbex.com
Open Graph description is not detected on the main page of Openbex. 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: