Tools & Wizards About Us
azores.gov.pt screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

azores.gov.pt

Portal do Governo dos Açores - Portal

Page Load Speed

9.9 sec in total

First Response

1.1 sec

Resources Loaded

7.5 sec

Page Rendered

1.3 sec

azores.gov.pt screenshot

About Website

Visit azores.gov.pt now to see the best up-to-date Azores content for Portugal and also check out these interesting facts you probably never knew about azores.gov.pt

O seu ponto de entrada unificado no universo de informações do Governo Regional dos Açores.

Visit azores.gov.pt

Key Findings

We analyzed Azores.gov.pt page load time and found that the first response time was 1.1 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

azores.gov.pt performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value19.9 s

0/100

10%

TBT (Total Blocking Time)

Value1,250 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.245

51/100

15%

TTI (Time to Interactive)

Value30.0 s

0/100

10%

Network Requests Diagram

portal.azores.gov.pt

1112 ms

font-awesome.min.css

30 ms

clay.css

44 ms

main.css

961 ms

combo

558 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Azores.gov.pt, 1% (1 request) were made to Stackpath.bootstrapcdn.com and 1% (1 request) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Portal.azores.gov.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 402.1 kB (6%)

Content Size

6.4 MB

After Optimization

6.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Azores.gov.pt main page is 6.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. 40% of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 201.8 kB

  • Original 219.5 kB
  • After minification 88.9 kB
  • After compression 17.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 130.6 kB, which is 59% 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 201.8 kB or 92% of the original size.

Image Optimization

-3%

Potential reduce by 199.8 kB

  • Original 6.0 MB
  • After minification 5.8 MB

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. Azores images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 230 B

  • Original 49.9 kB
  • After minification 49.9 kB
  • After compression 49.7 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.

CSS Optimization

-0%

Potential reduce by 303 B

  • Original 103.1 kB
  • After minification 103.1 kB
  • After compression 102.8 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. Azores.gov.pt has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (37%)

Requests Now

70

After Optimization

44

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

portal.azores.gov.pt

portal.azores.gov.pt

1112 ms

font-awesome.min.css

font-awesome.min.css

30 ms

clay.css

clay.css

44 ms

main.css

main.css

961 ms

combo

combo

558 ms

main.css

main.css

67 ms

combo

combo

556 ms

definicoespadrao.svg

definicoespadrao.svg

574 ms

altocontraste.svg

altocontraste.svg

581 ms

apenastexto.svg

apenastexto.svg

788 ms

tamanhodafonte.svg

tamanhodafonte.svg

1091 ms

regular_bell.svg

regular_bell.svg

1097 ms

close.svg

close.svg

597 ms

location.svg

location.svg

1115 ms

definicoes.svg

definicoes.svg

615 ms

hamburger_icon.png

hamburger_icon.png

509 ms

gra_logo_pt.svg

gra_logo_pt.svg

1062 ms

icone_menu_governo.svg

icone_menu_governo.svg

1196 ms

icone_menu_servicos.svg

icone_menu_servicos.svg

1373 ms

icone_menu_temas.svg

icone_menu_temas.svg

995 ms

icone_menu_acores.svg

icone_menu_acores.svg

1505 ms

icone_menu_comunicacao.svg

icone_menu_comunicacao.svg

1524 ms

search-icon-small.svg

search-icon-small.svg

1539 ms

4.svg

4.svg

1604 ms

cross_new.png

cross_new.png

1209 ms

search.png

search.png

1230 ms

login.svg

login.svg

1806 ms

telephone.png

telephone.png

1389 ms

envelope.svg

envelope.svg

1931 ms

user.svg

user.svg

1524 ms

cross-out.png

cross-out.png

1545 ms

eye_hide.svg

eye_hide.svg

1547 ms

main.css

main.css

1553 ms

select2.min.css

select2.min.css

1561 ms

main.css

main.css

1564 ms

main.css

main.css

1577 ms

main.css

main.css

1587 ms

main.css

main.css

1583 ms

arrow-up.svg

arrow-up.svg

2124 ms

leaflet.css

leaflet.css

55 ms

jquery-ui.min.css

jquery-ui.min.css

49 ms

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

81 ms

combo

combo

1625 ms

rocket-loader.min.js

rocket-loader.min.js

1176 ms

4ba829ca-74db-cdc5-b098-a15113c657c2

4ba829ca-74db-cdc5-b098-a15113c657c2

2439 ms

9760a262-a7bc-8893-ff86-581cec9e7930

9760a262-a7bc-8893-ff86-581cec9e7930

2408 ms

4fca94df-70a7-5eac-d4dc-c80257b1eda2

4fca94df-70a7-5eac-d4dc-c80257b1eda2

2142 ms

524384e1-8896-6b28-4ab0-9366849b083c

524384e1-8896-6b28-4ab0-9366849b083c

1799 ms

fac19652-f0e7-f5bd-36d3-5e6411848ee1

fac19652-f0e7-f5bd-36d3-5e6411848ee1

2786 ms

more.svg

more.svg

2163 ms

2024f3db-61f3-72a6-6f4d-50aacc476a3d

2024f3db-61f3-72a6-6f4d-50aacc476a3d

1862 ms

camera_detail.svg

camera_detail.svg

2243 ms

audio_detail.svg

audio_detail.svg

2184 ms

065fe01a-c681-bf7e-402c-7a6bf9cdc344

065fe01a-c681-bf7e-402c-7a6bf9cdc344

2948 ms

a235c854-93dc-f256-9dd2-5fa3e3a9cc45

a235c854-93dc-f256-9dd2-5fa3e3a9cc45

2021 ms

5c8be9da-c3c6-2b76-f516-208db217d738

5c8be9da-c3c6-2b76-f516-208db217d738

2019 ms

b8b71721-7bf7-6bd3-4b8a-eb661160050e

b8b71721-7bf7-6bd3-4b8a-eb661160050e

2093 ms

607c405e-ae5e-0c43-0d76-6fee3d002c36

607c405e-ae5e-0c43-0d76-6fee3d002c36

1981 ms

icon-hp-25.svg

icon-hp-25.svg

2409 ms

themes-public-consultation.svg

themes-public-consultation.svg

2455 ms

themes-participate-budget.svg

themes-participate-budget.svg

2332 ms

themes-open-data.svg

themes-open-data.svg

2338 ms

themes-contact.svg

themes-contact.svg

2302 ms

get_file

get_file

2256 ms

external-link.png

external-link.png

2181 ms

get_file

get_file

2344 ms

get_file

get_file

2335 ms

get_file

get_file

2364 ms

ipma.png

ipma.png

2248 ms

footerLogos.svg

footerLogos.svg

2268 ms

Lato-Light.ttf

Lato-Light.ttf

2543 ms

Lato-Thin.ttf

Lato-Thin.ttf

2825 ms

Lato-Regular.ttf

Lato-Regular.ttf

2622 ms

Lato-Bold.ttf

Lato-Bold.ttf

2612 ms

Lato-Black.ttf

Lato-Black.ttf

2646 ms

combo

combo

960 ms

Accessibility Review

azores.gov.pt accessibility score

84

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

Image elements do not have [alt] attributes

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.

Best Practices

azores.gov.pt best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

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

High

Page has valid source maps

SEO Factors

azores.gov.pt SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

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

    PT

  • Encoding

    UTF-8

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

azores.gov.pt

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