Tools & Wizards About Us
spm.pt screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    67% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

spm.pt

SPM | Sociedade Portuguesa de Matemáticahttps://www.spm.pt/-

Page Load Speed

8.4 sec in total

First Response

549 ms

Resources Loaded

4.5 sec

Page Rendered

3.4 sec

spm.pt screenshot

About Website

Welcome to spm.pt homepage info - get ready to check SPM best content for Portugal right away, or after learning these important things about spm.pt

A Sociedade Portuguesa de Matemática (SPM) é uma associação dedicada à divulgação, ao desenvolvimento do ensino e da investigação matemática em Portugal.

Visit spm.pt

Key Findings

We analyzed Spm.pt page load time and found that the first response time was 549 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

spm.pt performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value25.6 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

spm.pt

549 ms

spm.pt

458 ms

www.spm.pt

1091 ms

css2

41 ms

animate.css

111 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 83% of them (43 requests) were addressed to the original Spm.pt, 12% (6 requests) were made to Portal.spm.pt and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Portal.spm.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.6 MB (36%)

Content Size

7.2 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 48.4 kB

  • Original 56.1 kB
  • After minification 48.3 kB
  • After compression 7.7 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 7.8 kB, which is 14% 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 48.4 kB or 86% of the original size.

Image Optimization

-36%

Potential reduce by 2.5 MB

  • Original 6.9 MB
  • After minification 4.4 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. Obviously, SPM needs image optimization as it can save up to 2.5 MB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-30%

Potential reduce by 51.9 kB

  • Original 170.9 kB
  • After minification 170.9 kB
  • After compression 118.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 51.9 kB or 30% of the original size.

CSS Optimization

-5%

Potential reduce by 1.8 kB

  • Original 37.5 kB
  • After minification 37.5 kB
  • After compression 35.7 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. Spm.pt has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (50%)

Requests Now

44

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SPM. 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 JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

spm.pt

spm.pt

549 ms

spm.pt

spm.pt

458 ms

www.spm.pt

www.spm.pt

1091 ms

css2

css2

41 ms

animate.css

animate.css

111 ms

icomoon.css

icomoon.css

220 ms

bootstrap.min.css

bootstrap.min.css

441 ms

flexslider.css

flexslider.css

323 ms

owl.carousel.min.css

owl.carousel.min.css

323 ms

owl.theme.default.min.css

owl.theme.default.min.css

320 ms

style.css

style.css

330 ms

mystyle.css

mystyle.css

323 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

429 ms

b031b7a250.js

b031b7a250.js

45 ms

jquery.min.js

jquery.min.js

544 ms

jquery-1.12.4.js

jquery-1.12.4.js

661 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

425 ms

bootstrap.min.js

bootstrap.min.js

541 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

534 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

530 ms

owl.carousel.min.js

owl.carousel.min.js

560 ms

jquery.countTo.js

jquery.countTo.js

635 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

640 ms

main.js

main.js

645 ms

jquery.validate.js

jquery.validate.js

642 ms

jquery.validate.min.js

jquery.validate.min.js

640 ms

spm.js

spm.js

909 ms

banner1.png

banner1.png

1495 ms

banner2.png

banner2.png

231 ms

loader.gif

loader.gif

473 ms

spm.png

spm.png

211 ms

spm_grande.jpg

spm_grande.jpg

212 ms

henrique-manuel-guimaraes-300x300%20(2).jpg

henrique-manuel-guimaraes-300x300%20(2).jpg

472 ms

_MG_5574.jpg

_MG_5574.jpg

523 ms

image%20(98).jpg

image%20(98).jpg

883 ms

8imm.jpg

8imm.jpg

470 ms

2017_FCT_H_cor.jpg

2017_FCT_H_cor.jpg

471 ms

MEduc_H.jpg

MEduc_H.jpg

729 ms

spm2.png

spm2.png

727 ms

cartaz_enspm2022.png

cartaz_enspm2022.png

591 ms

saladeduvidas.png

saladeduvidas.png

1361 ms

olimpiadasmatematica.png

olimpiadasmatematica.png

1166 ms

spm_grande.jpg

spm_grande.jpg

1026 ms

ciencia_viva.jpg

ciencia_viva.jpg

1068 ms

fundacao_calouste_gulbenkian.jpg

fundacao_calouste_gulbenkian.jpg

1011 ms

banner2.png

banner2.png

1046 ms

banner3.png

banner3.png

1006 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPA.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPA.woff

305 ms

icomoon.ttf

icomoon.ttf

485 ms

icomoon.ttf

icomoon.ttf

715 ms

cartaz_enspm2022.png

cartaz_enspm2022.png

1102 ms

1encontro.png

1encontro.png

297 ms

Accessibility Review

spm.pt accessibility score

78

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.

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

High

Page has valid source maps

SEO Factors

spm.pt SEO score

72

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spm.pt can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Spm.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

spm.pt

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