Tools & Wizards About Us
spm.pt screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

spm.pt

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

Page Load Speed

4.1 sec in total

First Response

295 ms

Resources Loaded

3.4 sec

Page Rendered

450 ms

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 295 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

spm.pt performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

spm.pt

295 ms

spm.pt

396 ms

www.spm.pt

1053 ms

css2

41 ms

animate.css

289 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 86% of them (44 requests) were addressed to the original Spm.pt, 8% (4 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.1 sec) belongs to the original domain Spm.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 994.8 kB (24%)

Content Size

4.2 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Spm.pt main page is 4.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 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 48.2 kB

  • Original 55.3 kB
  • After minification 47.9 kB
  • After compression 7.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 7.3 kB, which is 13% 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.2 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 176.2 kB

  • Original 3.2 MB
  • After minification 3.0 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. SPM images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 529.6 kB

  • Original 685.4 kB
  • After minification 516.1 kB
  • After compression 155.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 529.6 kB or 77% of the original size.

CSS Optimization

-87%

Potential reduce by 240.8 kB

  • Original 276.5 kB
  • After minification 246.3 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 needs all CSS files to be minified and compressed as it can save up to 240.8 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

45

After Optimization

23

  • Images
  • JavaScript
  • CSS

The browser has sent 45 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

295 ms

spm.pt

spm.pt

396 ms

www.spm.pt

www.spm.pt

1053 ms

css2

css2

41 ms

animate.css

animate.css

289 ms

icomoon.css

icomoon.css

386 ms

bootstrap.min.css

bootstrap.min.css

577 ms

flexslider.css

flexslider.css

296 ms

owl.carousel.min.css

owl.carousel.min.css

293 ms

owl.theme.default.min.css

owl.theme.default.min.css

301 ms

style.css

style.css

391 ms

mystyle.css

mystyle.css

395 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

487 ms

b031b7a250.js

b031b7a250.js

108 ms

jquery.min.js

jquery.min.js

602 ms

jquery-1.12.4.js

jquery-1.12.4.js

861 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

416 ms

bootstrap.min.js

bootstrap.min.js

610 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

597 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

526 ms

owl.carousel.min.js

owl.carousel.min.js

592 ms

jquery.countTo.js

jquery.countTo.js

612 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

624 ms

main.js

main.js

694 ms

jquery.validate.js

jquery.validate.js

700 ms

jquery.validate.min.js

jquery.validate.min.js

711 ms

spm.js

spm.js

711 ms

olimpiadasmatematica.png

olimpiadasmatematica.png

835 ms

loader.gif

loader.gif

121 ms

spm.png

spm.png

121 ms

spmtestes2024_marco.png

spmtestes2024_marco.png

121 ms

centroformacao%20JANMAR24.jpg

centroformacao%20JANMAR24.jpg

418 ms

OPM_42.png

OPM_42.png

233 ms

suportes-olimpiadas-CPLP-cover-face_A.png

suportes-olimpiadas-CPLP-cover-face_A.png

204 ms

Novo%20Projeto%20(6).png

Novo%20Projeto%20(6).png

602 ms

spm_norte_.jpg

spm_norte_.jpg

232 ms

spm_grande.jpg

spm_grande.jpg

232 ms

spm_centro.png

spm_centro.png

307 ms

Muhnac.jpg

Muhnac.jpg

559 ms

enspm2024_r2.jpg

enspm2024_r2.jpg

349 ms

premioalvarobatistagoncalves2024.jpg

premioalvarobatistagoncalves2024.jpg

448 ms

multipli_online.jpg

multipli_online.jpg

453 ms

2017_FCT_H_cor.jpg

2017_FCT_H_cor.jpg

454 ms

MEduc_H.jpg

MEduc_H.jpg

523 ms

spm2.png

spm2.png

561 ms

spm_grande.jpg

spm_grande.jpg

639 ms

ciencia_viva.jpg

ciencia_viva.jpg

641 ms

fundacao_calouste_gulbenkian.jpg

fundacao_calouste_gulbenkian.jpg

550 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPA.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPA.woff

71 ms

icomoon.ttf

icomoon.ttf

522 ms

icomoon.ttf

icomoon.ttf

511 ms

Accessibility Review

spm.pt accessibility score

81

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

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: