Tools & Wizards About Us
webuild.pt screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

webuild.pt

Gestão documental | Desenho de processos | BPM | Webuild

Page Load Speed

8.4 sec in total

First Response

1.2 sec

Resources Loaded

6.9 sec

Page Rendered

253 ms

webuild.pt screenshot

About Website

Welcome to webuild.pt homepage info - get ready to check Webuild best content right away, or after learning these important things about webuild.pt

A Webuild é uma empresa especializada na implementação de soluções de gestão documental, desenvolvimento de software, na prestação de serviços de consultoria em sistemas de informação e desenho de pro...

Visit webuild.pt

Key Findings

We analyzed Webuild.pt page load time and found that the first response time was 1.2 sec and then it took 7.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

webuild.pt performance score

0

Network Requests Diagram

webuild.pt

1217 ms

font-awesome.css

10 ms

0_font_Aaux_Pro.css

647 ms

2_generic_tools.css

644 ms

3_gcmContent.css

648 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 63% of them (57 requests) were addressed to the original Webuild.pt, 9% (8 requests) were made to Apis.google.com and 3% (3 requests) were made to V2.zopim.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Webuild.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (64%)

Content Size

2.8 MB

After Optimization

992.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Webuild.pt main page is 2.8 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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 103.2 kB

  • Original 140.3 kB
  • After minification 138.0 kB
  • After compression 37.0 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 103.2 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 27.3 kB

  • Original 445.0 kB
  • After minification 417.8 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. Webuild images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 1.5 MB

  • Original 2.0 MB
  • After minification 1.9 MB
  • After compression 506.5 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 1.5 MB or 75% of the original size.

CSS Optimization

-82%

Potential reduce by 136.2 kB

  • Original 166.8 kB
  • After minification 130.8 kB
  • After compression 30.7 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. Webuild.pt needs all CSS files to be minified and compressed as it can save up to 136.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (71%)

Requests Now

84

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webuild.pt

webuild.pt

1217 ms

font-awesome.css

font-awesome.css

10 ms

0_font_Aaux_Pro.css

0_font_Aaux_Pro.css

647 ms

2_generic_tools.css

2_generic_tools.css

644 ms

3_gcmContent.css

3_gcmContent.css

648 ms

Ajax.css

Ajax.css

399 ms

Ajax.Default.css

Ajax.Default.css

895 ms

prettyPhoto.alpha.css

prettyPhoto.alpha.css

523 ms

prettyPhoto.css

prettyPhoto.css

784 ms

prettyPhoto.default.css

prettyPhoto.default.css

1230 ms

prettyPhoto.intro.css

prettyPhoto.intro.css

1231 ms

prettyPhoto.simple.css

prettyPhoto.simple.css

1235 ms

Window.Alert.css

Window.Alert.css

1122 ms

Window.css

Window.css

1542 ms

Window.Default.css

Window.Default.css

1542 ms

uniform.default.css

uniform.default.css

1303 ms

3_project_specific.css

3_project_specific.css

1728 ms

9_nivoslider.css

9_nivoslider.css

1616 ms

ListagemGrid.ComboBox.css

ListagemGrid.ComboBox.css

1920 ms

ListagemGrid.ComboBox.Default.css

ListagemGrid.ComboBox.Default.css

1917 ms

ListagemGrid.Grid.css

ListagemGrid.Grid.css

1921 ms

ecommerce.js

ecommerce.js

1977 ms

formGeneric.js

formGeneric.js

1978 ms

global.js

global.js

2205 ms

telerik.js

telerik.js

2206 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

2472 ms

swfobject_modified.js

swfobject_modified.js

2476 ms

WebResource.axd

WebResource.axd

220 ms

WebResource.axd

WebResource.axd

326 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

1330 ms

jquery.uniform.min.js

jquery.uniform.min.js

766 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

876 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

1957 ms

in.js

in.js

5 ms

addthis_widget.js

addthis_widget.js

10 ms

logo_webuild-798.png

logo_webuild-798.png

881 ms

logo_webuildPrint-799.png

logo_webuildPrint-799.png

880 ms

highlight_tdhotels-801.jpg

highlight_tdhotels-801.jpg

1202 ms

highlight_fertagus-802.jpg

highlight_fertagus-802.jpg

1850 ms

highlight_vilamoura-803.jpg

highlight_vilamoura-803.jpg

1850 ms

highlight_hourpoint-807.jpg

highlight_hourpoint-807.jpg

1207 ms

back_globalTitle.png

back_globalTitle.png

1025 ms

logo_webuildfx.png

logo_webuildfx.png

1025 ms

footer_backTop.png

footer_backTop.png

1241 ms

aauxpromedium-webfont.woff

aauxpromedium-webfont.woff

1274 ms

aauxprolight-webfont.woff

aauxprolight-webfont.woff

1266 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

13 ms

secureAnonymousFramework

secureAnonymousFramework

156 ms

logos_cert.png

logos_cert.png

1326 ms

aauxprobold-webfont.woff

aauxprobold-webfont.woff

1770 ms

analytics.js

analytics.js

81 ms

300lo.json

300lo.json

81 ms

all.js&version=v2.0

all.js&version=v2.0

117 ms

widgets.js

widgets.js

347 ms

plusone.js

plusone.js

77 ms

sprite.png

sprite.png

1743 ms

sprite_x.png

sprite_x.png

1742 ms

sprite_y.png

sprite_y.png

1743 ms

loader.gif

loader.gif

1744 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

95 ms

share

share

143 ms

sprite_connect_v14.png

sprite_connect_v14.png

112 ms

collect

collect

39 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

90 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

91 ms

fastbutton

fastbutton

250 ms

315 ms

widget_v2.134.js

widget_v2.134.js

32 ms

xd_arbiter.php

xd_arbiter.php

32 ms

xd_arbiter.php

xd_arbiter.php

216 ms

postmessageRelay

postmessageRelay

82 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

31 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

32 ms

popup.aspx

popup.aspx

1635 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

30 ms

rpc:shindig_random.js

rpc:shindig_random.js

37 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

__$$__stringtable_lang_pt.js

__$$__stringtable_lang_pt.js

4 ms

avatar_simple_visitor.png

avatar_simple_visitor.png

127 ms

aL63HcygAAVYuCCsAAA==

aL63HcygAAVYuCCsAAA==

13 ms

popup.css

popup.css

173 ms

WebResource.axd

WebResource.axd

116 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

346 ms

jquery.uniform.min.js

jquery.uniform.min.js

243 ms

imagem-comunicado-popup_optim-1155.png

imagem-comunicado-popup_optim-1155.png

473 ms

ie.css

ie.css

153 ms

print.css

print.css

243 ms

ping

ping

57 ms

like.php

like.php

88 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

19 ms

SEO Factors

webuild.pt SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webuild.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Webuild.pt main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

webuild.pt

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