Tools & Wizards About Us
tretas.org screenshot

Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

tretas.org

PáginaPrincipal - Tretas.org

Page Load Speed

1.7 sec in total

First Response

157 ms

Resources Loaded

1.4 sec

Page Rendered

114 ms

tretas.org screenshot

About Website

Visit tretas.org now to see the best up-to-date Tretas content for Portugal and also check out these interesting facts you probably never knew about tretas.org

Wiki onde se pretende reunir informação disponível nos meios de comunicação social 'main stream' portugueses sobre as práticas de bom governo (ou não) observadas neste país de brandos e corruptos cost...

Visit tretas.org

Key Findings

We analyzed Tretas.org page load time and found that the first response time was 157 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

tretas.org performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

95/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.1 s

99/100

10%

Network Requests Diagram

tretas.org

157 ms

tretas.org

340 ms

common.js

183 ms

style.css

181 ms

jquery-1.11.1.min.js

330 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 65% of them (20 requests) were addressed to the original Tretas.org, 10% (3 requests) were made to Platform.twitter.com and 6% (2 requests) were made to Redditstatic.com. The less responsive or slowest element that took the longest time to load (548 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 116.1 kB (56%)

Content Size

209.1 kB

After Optimization

93.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tretas.org main page is 209.1 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. 15% of websites need less resources to load. Javascripts take 110.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 13.5 kB

  • Original 18.8 kB
  • After minification 18.7 kB
  • After compression 5.3 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 13.5 kB or 72% of the original size.

Image Optimization

-17%

Potential reduce by 9.6 kB

  • Original 55.2 kB
  • After minification 45.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. Obviously, Tretas needs image optimization as it can save up to 9.6 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 73.7 kB

  • Original 110.5 kB
  • After minification 104.1 kB
  • After compression 36.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 73.7 kB or 67% of the original size.

CSS Optimization

-79%

Potential reduce by 19.3 kB

  • Original 24.6 kB
  • After minification 18.0 kB
  • After compression 5.3 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. Tretas.org needs all CSS files to be minified and compressed as it can save up to 19.3 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (55%)

Requests Now

29

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tretas.org

tretas.org

157 ms

tretas.org

tretas.org

340 ms

common.js

common.js

183 ms

style.css

style.css

181 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

330 ms

widgets.js

widgets.js

29 ms

button1.js

button1.js

23 ms

bombolom.css

bombolom.css

35 ms

admonition.css

admonition.css

36 ms

links.css

links.css

35 ms

comments.css

comments.css

69 ms

attach_list.css

attach_list.css

70 ms

comments.css

comments.css

70 ms

definition_list.css

definition_list.css

102 ms

ShowBlockIfLogin.css

ShowBlockIfLogin.css

105 ms

tables.css

tables.css

103 ms

tretas.png

tretas.png

39 ms

P%C3%A1ginaPrincipal

P%C3%A1ginaPrincipal

76 ms

P%C3%A1ginaPrincipal

P%C3%A1ginaPrincipal

119 ms

feedicon.png

feedicon.png

45 ms

bullet-bombolom.png

bullet-bombolom.png

44 ms

button1.html

button1.html

68 ms

like.php

like.php

84 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

3 ms

moin-www2.png

moin-www2.png

36 ms

tweet_button.6a78875565a912489e9aef879c881358.pt.html

tweet_button.6a78875565a912489e9aef879c881358.pt.html

15 ms

button-embed.js

button-embed.js

7 ms

button_info.json

button_info.json

50 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

485 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

548 ms

jot

jot

82 ms

Accessibility Review

tretas.org accessibility score

77

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

tretas.org best practices score

67

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

tretas.org SEO score

79

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

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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 Tretas.org 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 Tretas.org 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

tretas.org

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