4.2 sec in total
415 ms
3.4 sec
441 ms
Welcome to wengo.pt homepage info - get ready to check Wengo best content for Portugal right away, or after learning these important things about wengo.pt
Mais de 100 Especialistas Wengo disponíveis 24h por dia, todos os dias, em todas as áreas. Os nossos Especialistas respondem a todas as suas questões e são avaliados pelos clientes.
Visit wengo.ptWe analyzed Wengo.pt page load time and found that the first response time was 415 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
wengo.pt performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value6.5 s
9/100
25%
Value7.6 s
26/100
10%
Value16,770 ms
0/100
30%
Value0.017
100/100
15%
Value24.3 s
0/100
10%
415 ms
578 ms
65 ms
80 ms
587 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Wengo.pt, 41% (47 requests) were made to Www2.wgcdn.net and 39% (45 requests) were made to Www1.wgcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Www1.wgcdn.net.
Page size can be reduced by 960.3 kB (55%)
1.7 MB
772.6 kB
In fact, the total size of Wengo.pt main page is 1.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. 60% of websites need less resources to load. CSS take 633.5 kB which makes up the majority of the site volume.
Potential reduce by 50.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 9.6 kB, which is 15% 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 50.9 kB or 79% of the original size.
Potential reduce by 37.4 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. Wengo images are well optimized though.
Potential reduce by 322.8 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 322.8 kB or 69% of the original size.
Potential reduce by 549.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. Wengo.pt needs all CSS files to be minified and compressed as it can save up to 549.1 kB or 87% of the original size.
Number of requests can be reduced by 44 (41%)
107
63
The browser has sent 107 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 31 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
wengo.pt
415 ms
www.wengo.pt
578 ms
css
65 ms
css
80 ms
jquery.pack.js
587 ms
jquery.wSlideV.js
504 ms
jquery.jcarousel.min.js
501 ms
jquery.backgroundPosition.js
515 ms
jquery.taconite.js
497 ms
jquery.autogrow.js
514 ms
jquery.hint.js
515 ms
jquery.cycle.all.js
501 ms
jquery.snow.js
500 ms
isolate_jquery.js
581 ms
ajaxfileupload.js
496 ms
cufon-yui.js
504 ms
DinRegular_400.font.js
609 ms
cufon-init.js
606 ms
jquery-calendar.js
612 ms
wengo_channelizer_v2.js
568 ms
form2.js
609 ms
thickbox.js
610 ms
intradiv_taco.js
657 ms
jquery.slider.min.js
570 ms
crm.js
662 ms
swfobject.js
660 ms
login_block.js
683 ms
wg-cards.js
684 ms
wg-chat.l10n.por.js
711 ms
wg-chat.prod.js
570 ms
clickheat-original.js
596 ms
wg-raz.css
769 ms
wg-html-tags.css
597 ms
wg-main.css
750 ms
wg-widgets.css
779 ms
wl_wengo_partner_fix.css
791 ms
skin.css
796 ms
jquery.themaform.theme.intradiv-0.1.css
645 ms
thickbox.css
797 ms
wg-chat.css
799 ms
jquery-calendar.css
812 ms
jquery.slider.min.css
651 ms
wl_wengo_fix.css
816 ms
wg-cards.css
763 ms
slider.js
847 ms
ga-navigation-overlay.js
857 ms
ga.js
6 ms
ico_fra.jpg
738 ms
wengo-logo.jpg
128 ms
ico-user.jpg
198 ms
button_login.png
211 ms
ico_esl.jpg
790 ms
ico_usa.jpg
814 ms
ico_ita.jpg
877 ms
ico_bra.jpg
895 ms
ico_deu.jpg
943 ms
ico_tur.jpg
965 ms
ico_ell.jpg
996 ms
ico_eng.jpg
1005 ms
wengo_slide_01.jpg
327 ms
wengo_slide_02.jpg
280 ms
wengo_slide_03.jpg
328 ms
wengo_slide_04.jpg
248 ms
wengo_slide_05.jpg
273 ms
tarologa-sonia-veenstra-1834703.jpg
235 ms
tarologa-alexandra-1777482.jpg
509 ms
cartomante-sofia-velez-1567550.jpg
716 ms
tarologa-dana-2097438.jpg
1169 ms
pai-de-santo-sacerdote-coach-spiritual-adao-tarot-buzios-numerologia-2120833.jpg
1185 ms
simbologista-e-terapeuta-annah-simbologista-e-terapeuta-2180139.jpg
1091 ms
cartomante-teresa-cartomante-1925547.jpg
1131 ms
tarologo-astrogildo-motta-2014942.jpg
977 ms
vidente-daiana-vidente-1343571.jpg
954 ms
tarologa-ana-1906656.jpg
1211 ms
tarologa-ana-lua-2035550.jpg
1176 ms
sensitiva-psicoterapeuta-holistica-ana-maria-olis-1941305.jpg
1283 ms
ico-05.png
1213 ms
ico-06.png
1258 ms
ico-07.png
1259 ms
ico-08.png
1264 ms
ico-09.png
1290 ms
ico-03.png
1293 ms
ico-01.png
1347 ms
ico-04.png
1339 ms
tarologa-dina-loureiro-1849878.jpg
196 ms
medium-maria-amaral-1504277.jpg
246 ms
tarologa-paula-1756945.jpg
170 ms
tarologa-astrologa-numerologa-esmeralda-tarologa-1931312.jpg
306 ms
cartomante-miguel-de-sousa-1661938.jpg
309 ms
tarologa-ivone-tarologa-1358568.jpg
252 ms
tarologa-maria-do-ceu-1388250.jpg
414 ms
tarologa-angelologa-numerologa-maria-caiola-1962729.jpg
470 ms
medium-elisabete-1568244.jpg
742 ms
tarologa-mara-yuri-1532062.jpg
1241 ms
tarologa-mar-1382497.jpg
1091 ms
tarologa-maria-1859450.jpg
1016 ms
tarologa-anabela-souza-1803346.jpg
974 ms
ico-vivendi.png
550 ms
ico-payment.png
630 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
91 ms
mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf
90 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
102 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
107 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
107 ms
ico-search.png
1319 ms
subfooter_bg.jpg
1489 ms
ico_close.png
668 ms
wg-rainbow-bar-horizontal.gif
857 ms
__utm.gif
57 ms
analytics.js
55 ms
intradiv-ajax-loader-2.gif
1268 ms
quote_l.jpg
1271 ms
quote_r.jpg
1318 ms
collect
51 ms
collect
11 ms
collect
27 ms
wengo.pt accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wengo.pt 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
wengo.pt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
PT
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wengo.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 French language. Our system also found out that Wengo.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.
wengo.pt
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: