Access oceanario.pt. Oceanário de Lisboa

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value10.2 s

9/100

10%

TBT (Total Blocking Time)

Value1,070 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.687

7/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

oceanario.pt

333 ms

www.oceanario.pt

1232 ms

theme-styles.css

241 ms

jquery-1.11.2.min.js

454 ms

owl.carousel.js

333 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 60% of them (50 requests) were addressed to the original Oceanario.pt, 6% (5 requests) were made to Gstatic.com and 6% (5 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Oceanario.pt.

Content Size

2.4 MB

After Optimization

2.2 MB

In fact, the total size of Oceanario.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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 77.2 kB

Original 89.3 kB
After minification 62.2 kB
After compression 12.1 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 27.1 kB, which is 30% 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 77.2 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 98.7 kB

Original 1.8 MB
After minification 1.7 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. Oceanario images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 94.0 kB

Original 465.7 kB
After minification 465.6 kB
After compression 371.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 94.0 kB or 20% of the original size.

CSS Optimization

-5%

Potential reduce by 3.6 kB

Original 69.4 kB
After minification 69.4 kB
After compression 65.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. Oceanario.pt has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

These are opportunities to improve keyboard navigation in your application.

High

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

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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/).

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

oceanario.pt

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Oceanário de Lisboa

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

oceanario.pt

www.oceanario.pt

theme-styles.css

jquery-1.11.2.min.js

owl.carousel.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

oceanario.pt

www.oceanario.pt

theme-styles.css

jquery-1.11.2.min.js

owl.carousel.js

api.js

jquery.carouFredSel-6.2.1-packed.js

jquery.touchSwipe.min.js

plugins.js

utils.js

form-helper.js

jquery.maxlength.js

jquery.inputmask.min.js

main.js

wejs

wejs

wejs

recaptcha__pt.js

150_logo-11900-2.png

logo.png

logo-print.png

arrow_left_off.png

home_slider_sizer.gif

o-que-fazer-em-lisboa_oceanario-e-teleferico-bilhete-combinado_desktop_1920x1000.jpg

home_slider_sizer_medium.gif

o-que-fazer-em-lisboa_oceanario-e-teleferico-bilhete-combinado_desktop_840x760.jpg

home_slider_sizer_small.gif

o-que-fazer-em-lisboa_oceanario-e-teleferico-bilhete-combinado_desktop_440x582.jpg

arrow_right_off.png

arrow_down.png

ico_route.png

ico_visits.png

revista-professores-um-oceano-para-ensinar-abril-2024_oceanario-de-lisboa_619x450.jpg

plus.png

7-motivos-para-visitar-o-oceanario-de-lisboa_aquario-central_619x450.jpg

um-mergulho-no-oceano_programa-de-mergulho_oceanario-de-lisboa_619x450.jpg

hp_ativ_1920x384_visitaguiada.jpg

hp_ativ_1920x384_festa.jpg

hp_ativ_1920x384_fado.jpg

hp_ativ_1920x384_dct.jpg

hp_ativ_1920x384_bebes.jpg

mergulha_com_o_vasco.jpg

insta_sizer_372x370.gif