Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

wengo.pt

Wengo | Consultas de Tarot por telefone, chat ou email.

Page Load Speed

4.2 sec in total

First Response

415 ms

Resources Loaded

3.4 sec

Page Rendered

441 ms

wengo.pt screenshot

About Website

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.pt

Key Findings

We 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.

Performance Metrics

wengo.pt performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value16,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value24.3 s

0/100

10%

Network Requests Diagram

wengo.pt

415 ms

www.wengo.pt

578 ms

css

65 ms

css

80 ms

jquery.pack.js

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 Optimization Overview & Recommendations

Page size can be reduced by 960.3 kB (55%)

Content Size

1.7 MB

After Optimization

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.

HTML Optimization

-79%

Potential reduce by 50.9 kB

  • Original 64.2 kB
  • After minification 54.5 kB
  • After compression 13.2 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.

Image Optimization

-7%

Potential reduce by 37.4 kB

  • Original 568.9 kB
  • After minification 531.6 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.

JavaScript Optimization

-69%

Potential reduce by 322.8 kB

  • Original 466.2 kB
  • After minification 412.8 kB
  • After compression 143.4 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.

CSS Optimization

-87%

Potential reduce by 549.1 kB

  • Original 633.5 kB
  • After minification 558.1 kB
  • After compression 84.4 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.

Requests Breakdown

Number of requests can be reduced by 44 (41%)

Requests Now

107

After Optimization

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.

Accessibility Review

wengo.pt accessibility score

68

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

wengo.pt best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wengo.pt SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    FR

  • Encoding

    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.

Social Sharing Optimization

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: