1.4 sec in total
585 ms
725 ms
122 ms
Click here to check amazing BST content for Portugal. Otherwise, check out these important facts you probably never knew about bst.pt
Visit bst.ptWe analyzed Bst.pt page load time and found that the first response time was 585 ms and then it took 847 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
bst.pt performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value2.8 s
82/100
25%
Value4.1 s
79/100
10%
Value30 ms
100/100
30%
Value0.17
70/100
15%
Value3.0 s
96/100
10%
585 ms
10 ms
14 ms
10 ms
12 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 69% of them (25 requests) were addressed to the original Bst.pt, 28% (10 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (585 ms) belongs to the original domain Bst.pt.
Page size can be reduced by 159.1 kB (10%)
1.6 MB
1.5 MB
In fact, the total size of Bst.pt main page is 1.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 0 B
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. HTML code on this page is well minified. This web page is already compressed.
Potential reduce by 5.4 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. BST images are well optimized though.
Potential reduce by 98.6 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 98.6 kB or 69% of the original size.
Potential reduce by 55.1 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. Bst.pt needs all CSS files to be minified and compressed as it can save up to 55.1 kB or 79% of the original size.
Number of requests can be reduced by 17 (71%)
24
7
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BST. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
bst.pt
585 ms
system.base.css
10 ms
system.menus.css
14 ms
system.messages.css
10 ms
system.theme.css
12 ms
field.css
12 ms
node.css
13 ms
user.css
15 ms
views.css
15 ms
ckeditor.css
15 ms
ctools.css
17 ms
style.css
21 ms
responsive.css
17 ms
jquery.min.js
30 ms
jquery.once.js
17 ms
drupal.js
26 ms
retina.js
26 ms
plugins.js
26 ms
global.js
26 ms
css
23 ms
logo.png
68 ms
slide-image-1.jpg
73 ms
slide-image-2.jpg
69 ms
slide-image-3.jpg
67 ms
slide-image-4.jpg
73 ms
uYKcPVoh6c5R0NpdEY5A-Q.woff
19 ms
DXI1ORHCpsQm3Vp6mXoaTRsxEYwM7FgeyaSgU71cLG0.woff
20 ms
MTP_ySUJH_bn48VBG8sNShsxEYwM7FgeyaSgU71cLG0.woff
19 ms
k3k702ZOKiLJc3WVjuplzBsxEYwM7FgeyaSgU71cLG0.woff
21 ms
EInbV5DfGHOiMmvb1Xr-hhsxEYwM7FgeyaSgU71cLG0.woff
22 ms
O4NhV7_qs9r9seTo7fnsVD8E0i7KZn-EPnyo3HZu7kw.woff
21 ms
PRmiXeptR36kaC0GEAetxv25ds880Du_gFZbUlZlsbg.woff
22 ms
PRmiXeptR36kaC0GEAetxsUW6j0fiq4_bYOAoMNnBhA.woff
21 ms
PRmiXeptR36kaC0GEAetxpXMLUeV6_io0G3F6eXSVcg.woff
17 ms
PRmiXeptR36kaC0GEAetxjZJchHK-lPtiIaM3GRtbZU.woff
16 ms
fontawesome-webfont.woff
16 ms
bst.pt accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
bst.pt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
bst.pt SEO score
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
Document uses legible font sizes
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bst.pt can be misinterpreted by Google and other search engines. Our service has detected that English 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 Bst.pt main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
bst.pt
Open Graph description is not detected on the main page of BST. 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: