Tools & Wizards About Us
capitaldomovel.pt screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

capitaldomovel.pt

60ª Capital do Móvel – Feira de Mobiliário e Decoração - Capital do Móvel

Page Load Speed

6.5 sec in total

First Response

337 ms

Resources Loaded

5.7 sec

Page Rendered

487 ms

capitaldomovel.pt screenshot

About Website

Click here to check amazing Capital Domovel content. Otherwise, check out these important facts you probably never knew about capitaldomovel.pt

60ª Capital do Móvel Prepare-se para vivenciar a maior feira de móveis e decoração, com o regresso da Capital do Móvel ao Porto! Durante nove dias consecutivos, de 02 a 10 de setembro, todos os holofo...

Visit capitaldomovel.pt

Key Findings

We analyzed Capitaldomovel.pt page load time and found that the first response time was 337 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

capitaldomovel.pt performance score

0

Network Requests Diagram

capitaldomovel.pt

337 ms

1320 ms

analytics.js

10 ms

collect

16 ms

wp-emoji-release.min.js

521 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Capitaldomovel.pt, 28% (38 requests) were made to Aepf.pt and 27% (36 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Aepf.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (55%)

Content Size

3.7 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Capitaldomovel.pt main page is 3.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. 65% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 90.3 kB

  • Original 108.0 kB
  • After minification 104.2 kB
  • After compression 17.7 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 90.3 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 35.1 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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. Capital Domovel images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 972.4 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 442.6 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 972.4 kB or 69% of the original size.

CSS Optimization

-90%

Potential reduce by 952.1 kB

  • Original 1.1 MB
  • After minification 994.1 kB
  • After compression 107.1 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. Capitaldomovel.pt needs all CSS files to be minified and compressed as it can save up to 952.1 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (54%)

Requests Now

127

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capital Domovel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

capitaldomovel.pt

capitaldomovel.pt

337 ms

1320 ms

analytics.js

analytics.js

10 ms

collect

collect

16 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

521 ms

styles.css

styles.css

215 ms

cli-style.css

cli-style.css

217 ms

plugins.css

plugins.css

930 ms

font-awesome.min.css

font-awesome.min.css

32 ms

animate.css

animate.css

725 ms

style.css

style.css

774 ms

custom.css

custom.css

427 ms

js_composer.min.css

js_composer.min.css

1329 ms

jquery.js

jquery.js

1088 ms

jquery-migrate.min.js

jquery-migrate.min.js

626 ms

cookielawinfo.js

cookielawinfo.js

734 ms

modernizr.min.js

modernizr.min.js

749 ms

pace.js

pace.js

863 ms

jquery.form.min.js

jquery.form.min.js

654 ms

scripts.js

scripts.js

722 ms

plugins.js

plugins.js

1277 ms

wow.js

wow.js

811 ms

validate.js

validate.js

925 ms

main.js

main.js

827 ms

wp-embed.min.js

wp-embed.min.js

922 ms

js_composer_front.min.js

js_composer_front.min.js

879 ms

js

js

83 ms

infobox.js

infobox.js

904 ms

google-hotel-map.js

google-hotel-map.js

968 ms

directions.js

directions.js

968 ms

api.js

api.js

48 ms

capitalmovel_logo.png

capitalmovel_logo.png

329 ms

CAPA.jpg

CAPA.jpg

1118 ms

imagem_abril_verde-1.png

imagem_abril_verde-1.png

915 ms

aepf.png

aepf.png

327 ms

capitaldomovel.png

capitaldomovel.png

328 ms

location-icon.png

location-icon.png

333 ms

email-icon.png

email-icon.png

332 ms

back_to_top.png

back_to_top.png

332 ms

overlay.png

overlay.png

332 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

3 ms

atc.min.js

atc.min.js

310 ms

widgets.js

widgets.js

236 ms

common.js

common.js

232 ms

map.js

map.js

266 ms

util.js

util.js

267 ms

marker.js

marker.js

265 ms

overlay.js

overlay.js

263 ms

controls.js

controls.js

261 ms

places_impl.js

places_impl.js

260 ms

recaptcha__en.js

recaptcha__en.js

236 ms

ajax-loader.gif

ajax-loader.gif

159 ms

bg_direction_nav.png

bg_direction_nav.png

158 ms

ajax-loader.gif

ajax-loader.gif

157 ms

infowindow.js

infowindow.js

85 ms

fallback

fallback

74 ms

master

master

39 ms

openhand_8_8.cur

openhand_8_8.cur

173 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

218 ms

PlaceService.FindPlaces

PlaceService.FindPlaces

375 ms

fallback__ltr.css

fallback__ltr.css

110 ms

payload

payload

146 ms

widgets.js

widgets.js

143 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

205 ms

stats.js

stats.js

135 ms

css

css

270 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

167 ms

transparent.png

transparent.png

150 ms

google4.png

google4.png

105 ms

mapcnt6.png

mapcnt6.png

106 ms

sv5.png

sv5.png

196 ms

css

css

213 ms

FAVICON_CAPITALDOMOVEL.png

FAVICON_CAPITALDOMOVEL.png

194 ms

google_white5.png

google_white5.png

109 ms

tmapctrl.png

tmapctrl.png

177 ms

cb_scout5.png

cb_scout5.png

179 ms

tmapctrl4.png

tmapctrl4.png

178 ms

imgs8.png

imgs8.png

177 ms

widget

widget

115 ms

vt

vt

126 ms

vt

vt

204 ms

vt

vt

161 ms

vt

vt

203 ms

vt

vt

205 ms

vt

vt

202 ms

vt

vt

205 ms

vt

vt

207 ms

vt

vt

243 ms

vt

vt

244 ms

vt

vt

242 ms

vt

vt

242 ms

vt

vt

245 ms

vt

vt

246 ms

vt

vt

289 ms

vt

vt

289 ms

vt

vt

289 ms

vt

vt

289 ms

vt

vt

292 ms

vt

vt

288 ms

vt

vt

334 ms

vt

vt

345 ms

vt

vt

333 ms

vt

vt

326 ms

vt

vt

330 ms

vt

vt

324 ms

vt

vt

369 ms

vt

vt

377 ms

vt

vt

388 ms

signed_in_api_icons2.png

signed_in_api_icons2.png

117 ms

logo_48.png

logo_48.png

102 ms

refresh.png

refresh.png

113 ms

audio.png

audio.png

112 ms

white_google_icon.png

white_google_icon.png

82 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

90 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

125 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

129 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

128 ms

vt

vt

321 ms

PlaceService.GetPlaceDetails

PlaceService.GetPlaceDetails

159 ms

PlaceService.GetPlaceDetails

PlaceService.GetPlaceDetails

120 ms

PlaceService.GetPlaceDetails

PlaceService.GetPlaceDetails

158 ms

PlaceService.GetPlaceDetails

PlaceService.GetPlaceDetails

117 ms

PlaceService.GetPlaceDetails

PlaceService.GetPlaceDetails

158 ms

PlaceService.GetPlaceDetails

PlaceService.GetPlaceDetails

201 ms

PlaceService.GetPlaceDetails

PlaceService.GetPlaceDetails

187 ms

PlaceService.GetPlaceDetails

PlaceService.GetPlaceDetails

379 ms

PlaceService.GetPlaceDetails

PlaceService.GetPlaceDetails

203 ms

vt

vt

305 ms

restaurant-71.png

restaurant-71.png

53 ms

shopping-71.png

shopping-71.png

53 ms

museum-71.png

museum-71.png

53 ms

bar-71.png

bar-71.png

53 ms

gas_station-71.png

gas_station-71.png

52 ms

cafe-71.png

cafe-71.png

58 ms

SEO Factors

capitaldomovel.pt SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Capitaldomovel.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Capitaldomovel.pt 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.

Social Sharing Optimization

capitaldomovel.pt

Open Graph description is not detected on the main page of Capital Domovel. 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: