Tools & Wizards About Us
greensavers.pt screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

greensavers.pt

Green Savers

Page Load Speed

3.8 sec in total

First Response

311 ms

Resources Loaded

2.9 sec

Page Rendered

531 ms

greensavers.pt screenshot

About Website

Welcome to greensavers.pt homepage info - get ready to check Green Savers best content right away, or after learning these important things about greensavers.pt

A revista portuguesa líder em notícias de sustentabilidade e ambiente

Visit greensavers.pt

Key Findings

We analyzed Greensavers.pt page load time and found that the first response time was 311 ms and then it took 3.5 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

greensavers.pt performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value13.0 s

12/100

10%

Network Requests Diagram

greensavers.pt

311 ms

greensavers.sapo.pt

595 ms

mas-tracker-min.js

63 ms

mas-push-min.js

73 ms

style.min.css

367 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Greensavers.pt, 44% (24 requests) were made to Greensavers.sapo.pt and 13% (7 requests) were made to Cmp.inmobi.com. The less responsive or slowest element that took the longest time to load (925 ms) relates to the external source Greensavers.sapo.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (68%)

Content Size

2.4 MB

After Optimization

770.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Greensavers.pt main page is 2.4 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. 70% of websites need less resources to load. CSS take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 182.2 kB

  • Original 219.6 kB
  • After minification 211.6 kB
  • After compression 37.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 182.2 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 14.5 kB

  • Original 395.9 kB
  • After minification 381.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. Green Savers images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 251.7 kB

  • Original 430.6 kB
  • After minification 430.1 kB
  • After compression 178.9 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 251.7 kB or 58% of the original size.

CSS Optimization

-87%

Potential reduce by 1.2 MB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 173.2 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. Greensavers.pt needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (62%)

Requests Now

45

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

greensavers.pt

greensavers.pt

311 ms

greensavers.sapo.pt

greensavers.sapo.pt

595 ms

mas-tracker-min.js

mas-tracker-min.js

63 ms

mas-push-min.js

mas-push-min.js

73 ms

style.min.css

style.min.css

367 ms

nc-egoi-form-public.css

nc-egoi-form-public.css

283 ms

bootstrap.min.css

bootstrap.min.css

33 ms

wp-night-mode-public.css

wp-night-mode-public.css

373 ms

js_composer.min.css

js_composer.min.css

746 ms

css

css

48 ms

jquery.min.js

jquery.min.js

465 ms

jquery-migrate.min.js

jquery-migrate.min.js

385 ms

nc-egoi-form-public.js

nc-egoi-form-public.js

371 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

44 ms

wp-night-mode-public.js

wp-night-mode-public.js

454 ms

78249b8c9994ef2b0d31f0dd9d45da14.css

78249b8c9994ef2b0d31f0dd9d45da14.css

925 ms

843218ed5958eb59130adf1090e49267.css

843218ed5958eb59130adf1090e49267.css

648 ms

bsuv3.min.js

bsuv3.min.js

668 ms

asyncjs.php

asyncjs.php

511 ms

lazypub.min.js

lazypub.min.js

590 ms

js

js

51 ms

js_composer_front.min.js

js_composer_front.min.js

392 ms

49839cea2d94c539cef412d822e06db8.js

49839cea2d94c539cef412d822e06db8.js

555 ms

greensavers_logo2.png

greensavers_logo2.png

94 ms

promise-7.0.4.min.js

promise-7.0.4.min.js

200 ms

logo-meo-energia-01.png

logo-meo-energia-01.png

140 ms

green_savers_14-300x400.jpg

green_savers_14-300x400.jpg

141 ms

newsletter-subscri%C3%A7%C3%A3o-e1663951069593.png

newsletter-subscri%C3%A7%C3%A3o-e1663951069593.png

839 ms

GS_logobranco.png

GS_logobranco.png

140 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

18 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

36 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

112 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uz.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uz.woff

109 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uz.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uz.woff

110 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uz.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uz.woff

111 ms

bsuv4.min.js

bsuv4.min.js

241 ms

25d1c6898db37060c918aa29c1d7bd72.js

25d1c6898db37060c918aa29c1d7bd72.js

236 ms

choice.js

choice.js

181 ms

asyncspc.php

asyncspc.php

147 ms

doublepimp2.js

doublepimp2.js

111 ms

js

js

263 ms

cmp2-polyfilled.js

cmp2-polyfilled.js

79 ms

geoip

geoip

6 ms

Tubarao-seda-900x450.jpg

Tubarao-seda-900x450.jpg

115 ms

cmp-list.json

cmp-list.json

2 ms

banner-900x450-1-900x450.jpg

banner-900x450-1-900x450.jpg

107 ms

Fielder-Wheat-Image-900x450.jpg

Fielder-Wheat-Image-900x450.jpg

108 ms

pastagens_acores.jpg

pastagens_acores.jpg

187 ms

douro-4768654_1280-1-750x430.jpg

douro-4768654_1280-1-750x430.jpg

109 ms

cmp2ui-pt.js

cmp2ui-pt.js

14 ms

analytics.js

analytics.js

8 ms

vendor-list-trimmed-v1.json

vendor-list-trimmed-v1.json

42 ms

collect

collect

80 ms

purposes-pt-pt.json

purposes-pt-pt.json

6 ms

collect

collect

31 ms

Accessibility Review

greensavers.pt accessibility score

86

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.

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

greensavers.pt best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

greensavers.pt SEO score

86

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

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greensavers.pt 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 Greensavers.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

greensavers.pt

Open Graph data is detected on the main page of Green Savers. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: