Tools & Wizards About Us
spq.pt screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

spq.pt

Início • Sociedade Portuguesa de Química

Page Load Speed

1.9 sec in total

First Response

178 ms

Resources Loaded

1.4 sec

Page Rendered

308 ms

spq.pt screenshot

About Website

Welcome to spq.pt homepage info - get ready to check Spq best content for Brazil right away, or after learning these important things about spq.pt

Sociedade Portuguesa de Química :: SPQ :: informação, ensino e actividades de química em Portugal

Visit spq.pt

Key Findings

We analyzed Spq.pt page load time and found that the first response time was 178 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

spq.pt performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value4.4 s

73/100

10%

TBT (Total Blocking Time)

Value240 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.435

21/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

spq.pt

178 ms

www.spq.pt

383 ms

bootstrap.min.css

53 ms

spq2.css

81 ms

ie10-viewport-bug-workaround.css

161 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 72% of them (44 requests) were addressed to the original Spq.pt, 7% (4 requests) were made to Maxcdn.bootstrapcdn.com and 5% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (838 ms) belongs to the original domain Spq.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.1 kB (10%)

Content Size

881.1 kB

After Optimization

797.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Spq.pt main page is 881.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 730.9 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 57.8 kB

  • Original 65.1 kB
  • After minification 37.1 kB
  • After compression 7.3 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 28.0 kB, which is 43% 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 57.8 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 23.7 kB

  • Original 730.9 kB
  • After minification 707.2 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. Spq images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 838 B

  • Original 74.7 kB
  • After minification 74.7 kB
  • After compression 73.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. This website has mostly compressed JavaScripts.

CSS Optimization

-17%

Potential reduce by 1.7 kB

  • Original 10.4 kB
  • After minification 10.4 kB
  • After compression 8.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. Spq.pt needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (31%)

Requests Now

54

After Optimization

37

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

spq.pt

spq.pt

178 ms

www.spq.pt

www.spq.pt

383 ms

bootstrap.min.css

bootstrap.min.css

53 ms

spq2.css

spq2.css

81 ms

ie10-viewport-bug-workaround.css

ie10-viewport-bug-workaround.css

161 ms

font-awesome.min.css

font-awesome.min.css

49 ms

font-awesome-animation.css

font-awesome-animation.css

51 ms

ekko-lightbox.css

ekko-lightbox.css

71 ms

jquery-ui.css

jquery-ui.css

38 ms

embed.js

embed.js

42 ms

js

js

74 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

39 ms

bootstrap.min.js

bootstrap.min.js

55 ms

portalvivo.js

portalvivo.js

232 ms

jquery-ui.min.js

jquery-ui.min.js

39 ms

ekko-lightbox.min.js

ekko-lightbox.min.js

75 ms

angular.min.js

angular.min.js

38 ms

pv-angular.js

pv-angular.js

304 ms

home-boletim.js

home-boletim.js

305 ms

front.js

front.js

306 ms

spq_logo.png

spq_logo.png

305 ms

banner.jpg

banner.jpg

838 ms

640_th.jpg

640_th.jpg

310 ms

636_th.jpg

636_th.jpg

334 ms

635_th.jpg

635_th.jpg

474 ms

633_th.jpg

633_th.jpg

408 ms

622_th.jpg

622_th.jpg

408 ms

623_th.jpg

623_th.jpg

408 ms

624_th.jpg

624_th.jpg

409 ms

625_th.jpg

625_th.jpg

474 ms

593_th.jpg

593_th.jpg

476 ms

616_th.jpg

616_th.jpg

477 ms

617_th.jpg

617_th.jpg

476 ms

592_th.jpg

592_th.jpg

552 ms

589_th.jpg

589_th.jpg

552 ms

586_th.jpg

586_th.jpg

556 ms

577_th.jpg

577_th.jpg

557 ms

578_th.jpg

578_th.jpg

557 ms

chemistry_europe_small.png

chemistry_europe_small.png

630 ms

CE%20Newsletter.png

CE%20Newsletter.png

631 ms

euchems_news.png

euchems_news.png

634 ms

57_th.jpg

57_th.jpg

634 ms

351_th.jpg

351_th.jpg

637 ms

quimica_verde_2023.jpg

quimica_verde_2023.jpg

710 ms

css

css

29 ms

%7B%7Bmagazine.cover_thumb%7D%7D

%7B%7Bmagazine.cover_thumb%7D%7D

555 ms

spq.png

spq.png

531 ms

chemistryviews.jpg

chemistryviews.jpg

532 ms

chempubsoc.jpg

chempubsoc.jpg

535 ms

euchems_2018.jpg

euchems_2018.jpg

607 ms

iupac.jpg

iupac.jpg

611 ms

efmc-new.jpg

efmc-new.jpg

611 ms

imsf.jpg

imsf.jpg

601 ms

iucr.jpg

iucr.jpg

517 ms

eusss.jpg

eusss.jpg

568 ms

eca.jpg

eca.jpg

573 ms

FCT_V_cor.jpg

FCT_V_cor.jpg

574 ms

2sDfZG1Wl4LcnbuKjk0j.ttf

2sDfZG1Wl4LcnbuKjk0j.ttf

86 ms

2sDcZG1Wl4LcnbuCJW8zaGW8.ttf

2sDcZG1Wl4LcnbuCJW8zaGW8.ttf

99 ms

2sDcZG1Wl4LcnbuCNWgzaGW8.ttf

2sDcZG1Wl4LcnbuCNWgzaGW8.ttf

117 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

85 ms

Accessibility Review

spq.pt accessibility score

81

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

spq.pt best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

spq.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 Spq.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 Spq.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

spq.pt

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