4.7 sec in total
187 ms
4.5 sec
72 ms
Visit wengo.com.br now to see the best up-to-date Wengo content for Brazil and also check out these interesting facts you probably never knew about wengo.com.br
Visit wengo.com.brWe analyzed Wengo.com.br page load time and found that the first response time was 187 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
wengo.com.br performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value14.0 s
0/100
25%
Value13.5 s
2/100
10%
Value2,650 ms
4/100
30%
Value0.876
3/100
15%
Value22.7 s
1/100
10%
187 ms
487 ms
624 ms
643 ms
282 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Wengo.com.br, 45% (25 requests) were made to Fonts.gstatic.com and 9% (5 requests) were made to Cdn2.astrocentro.com.br. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cdn.astrocentro.com.br.
Page size can be reduced by 95.8 kB (16%)
591.2 kB
495.4 kB
In fact, the total size of Wengo.com.br main page is 591.2 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. 40% of websites need less resources to load. Javascripts take 374.3 kB which makes up the majority of the site volume.
Potential reduce by 37.6 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 16.0 kB, which is 36% 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 37.6 kB or 85% of the original size.
Potential reduce by 0 B
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. Wengo images are well optimized though.
Potential reduce by 7.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.
Potential reduce by 51.0 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. Wengo.com.br needs all CSS files to be minified and compressed as it can save up to 51.0 kB or 31% of the original size.
Number of requests can be reduced by 22 (88%)
25
3
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wengo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
wengo.com.br
187 ms
wengo.com.br
487 ms
www.wengo.com.br
624 ms
astrocentro.com.br
643 ms
consultas-1270
282 ms
js
90 ms
owl.carousel.min.css
55 ms
owl.theme.default.min.css
66 ms
bootstrap.min.css
66 ms
easy-autocomplete.min.css
309 ms
main.desktop.min.css
465 ms
css
62 ms
styles.min.css
887 ms
gpt.js
121 ms
jquery-3.3.1.slim.min.js
45 ms
auth-component.js
689 ms
sharedbar.js
349 ms
desktop.min.js
397 ms
parse-twig-to-json.js
318 ms
conversion_async.js
116 ms
jquery.easy-autocomplete.min.js
317 ms
bootstrap.min.js
75 ms
index.js
966 ms
index.min.js
687 ms
css2
30 ms
gtm.js
104 ms
pubads_impl.js
14 ms
150684666
85 ms
logo-astrocentro.png
119 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXx-p7K4GLs.woff
38 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXx-p7K4GLvztg.woff
49 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw2aXx-p7K4GLvztg.woff
44 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw9aXx-p7K4GLvztg.woff
42 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw0aXx-p7K4GLvztg.woff
43 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff
48 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff
47 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff
48 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff
49 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff
48 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff
49 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXx-p7K4GLvztg.woff
49 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw2aXx-p7K4GLvztg.woff
60 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw9aXx-p7K4GLvztg.woff
61 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw0aXx-p7K4GLvztg.woff
61 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXx-p7K4GLs.woff
62 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXx-p7K4GLvztg.woff
61 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w2aXx-p7K4GLvztg.woff
61 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w9aXx-p7K4GLvztg.woff
62 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w0aXx-p7K4GLvztg.woff
63 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff
64 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4GLvztg.woff
63 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4GLvztg.woff
62 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLvztg.woff
64 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4GLvztg.woff
63 ms
sharedbar.bweh9hmi.js
1293 ms
wengo.com.br accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
wengo.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
wengo.com.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wengo.com.br 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 Wengo.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.
wengo.com.br
Open Graph description is not detected on the main page of Wengo. 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: