Tools & Wizards About Us
webg3.com.br screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

webg3.com.br

WebG3 - Sistema Online Para Cálculo de Esquadrias de Alumínio e Temperados

Page Load Speed

2.6 sec in total

First Response

319 ms

Resources Loaded

1.7 sec

Page Rendered

563 ms

webg3.com.br screenshot

About Website

Click here to check amazing WebG3 content for Brazil. Otherwise, check out these important facts you probably never knew about webg3.com.br

WebG3 - Sistema Online Para Cálculo de Esquadrias de Alumínio e Temperados. Visando as vantagens dos sistemas em Nuvem, a FORTMAX SISTEMAS investiu fortemente na criação de sistemas para esquadrias, s...

Visit webg3.com.br

Key Findings

We analyzed Webg3.com.br page load time and found that the first response time was 319 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

webg3.com.br performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.681

8/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

webg3.com.br

319 ms

216 ms

jquery

285 ms

jquery.dropotron.min.js

193 ms

skel.min.js

192 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 63% of them (32 requests) were addressed to the original Webg3.com.br, 12% (6 requests) were made to Fonts.gstatic.com and 8% (4 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (665 ms) belongs to the original domain Webg3.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 178.2 kB (19%)

Content Size

956.4 kB

After Optimization

778.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Webg3.com.br main page is 956.4 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. 60% of websites need less resources to load. Images take 488.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 114.9 kB

  • Original 149.4 kB
  • After minification 134.8 kB
  • After compression 34.4 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 114.9 kB or 77% of the original size.

Image Optimization

-9%

Potential reduce by 41.9 kB

  • Original 488.4 kB
  • After minification 446.5 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. WebG3 images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 13.5 kB

  • Original 294.6 kB
  • After minification 294.6 kB
  • After compression 281.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-33%

Potential reduce by 7.9 kB

  • Original 24.0 kB
  • After minification 24.0 kB
  • After compression 16.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. Webg3.com.br needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (52%)

Requests Now

42

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webg3.com.br

webg3.com.br

319 ms

216 ms

jquery

jquery

285 ms

jquery.dropotron.min.js

jquery.dropotron.min.js

193 ms

skel.min.js

skel.min.js

192 ms

skel-layers.min.js

skel-layers.min.js

194 ms

init.js

init.js

194 ms

jquery.bpopup.min.js

jquery.bpopup.min.js

193 ms

jquery.validate.min.js

jquery.validate.min.js

307 ms

jquery.qtip.js

jquery.qtip.js

383 ms

login.css

login.css

308 ms

jquery.qtip.css

jquery.qtip.css

306 ms

api.js

api.js

40 ms

style.css

style.css

98 ms

style-desktop.css

style-desktop.css

99 ms

style-1000px.css

style-1000px.css

100 ms

css

css

28 ms

font-awesome.min.css

font-awesome.min.css

98 ms

analytics.js

analytics.js

33 ms

recaptcha__en.js

recaptcha__en.js

162 ms

bg01.png

bg01.png

160 ms

logo-webg3-small.png

logo-webg3-small.png

313 ms

loading.GIF

loading.GIF

159 ms

otimizador-linear.jpg

otimizador-linear.jpg

314 ms

otimizador-bidimensional.jpg

otimizador-bidimensional.jpg

314 ms

pcp.jpg

pcp.jpg

314 ms

img-linear.jpg

img-linear.jpg

313 ms

img-bidimensional.jpg

img-bidimensional.jpg

313 ms

teamviewer.png

teamviewer.png

419 ms

aluminio.jpg

aluminio.jpg

665 ms

bg02.png

bg02.png

390 ms

bg03.png

bg03.png

391 ms

bg04.png

bg04.png

390 ms

arrow.png

arrow.png

388 ms

bg5.jpg

bg5.jpg

475 ms

sdk.js

sdk.js

128 ms

fbevents.js

fbevents.js

26 ms

collect

collect

182 ms

sdk.js

sdk.js

120 ms

fallback

fallback

85 ms

3457170941203667

3457170941203667

80 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

48 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

77 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

290 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

78 ms

fallback__ltr.css

fallback__ltr.css

39 ms

css

css

29 ms

logo_48.png

logo_48.png

24 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

5 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

6 ms

Accessibility Review

webg3.com.br accessibility score

81

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

webg3.com.br best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

webg3.com.br SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webg3.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Webg3.com.br 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

webg3.com.br

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