1.5 sec in total
184 ms
1 sec
318 ms
Visit audium.pt now to see the best up-to-date AUDIUM content and also check out these interesting facts you probably never knew about audium.pt
Visit audium.ptWe analyzed Audium.pt page load time and found that the first response time was 184 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
audium.pt performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value4.3 s
42/100
25%
Value3.7 s
86/100
10%
Value50 ms
100/100
30%
Value0.135
80/100
15%
Value3.6 s
91/100
10%
184 ms
64 ms
157 ms
154 ms
240 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 84% of them (27 requests) were addressed to the original Audium.pt, 6% (2 requests) were made to Google-analytics.com and 6% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (607 ms) belongs to the original domain Audium.pt.
Page size can be reduced by 254.2 kB (16%)
1.6 MB
1.4 MB
In fact, the total size of Audium.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. 40% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 16.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 16.9 kB or 79% of the original size.
Potential reduce by 45.9 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. AUDIUM images are well optimized though.
Potential reduce by 88.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 88.9 kB or 60% of the original size.
Potential reduce by 102.6 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. Audium.pt needs all CSS files to be minified and compressed as it can save up to 102.6 kB or 84% of the original size.
We found no issues to fix!
28
28
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AUDIUM. According to our analytics all requests are already optimized.
audium.pt
184 ms
css
64 ms
bootstrap.min.css
157 ms
geral.css
154 ms
jquery.min.js
240 ms
bootstrap.min.js
170 ms
ga.js
8 ms
logoi.png
105 ms
facebook.jpg
106 ms
servicos-web.png
105 ms
I-AUDITXVS2.JPG
447 ms
I-20150223X000120.JPG
534 ms
I-JUMBO1-1728X800XC.JPG
457 ms
I-SITEXAUDIUM.JPG
377 ms
I671-EDPXSEDE.JPG
378 ms
I670-ASSEMBLEIAXNACIONALXANGOLA.JPG
242 ms
I672-ALEGROSET.JPG
403 ms
I673-ASSEMBLEIAXNACIONALXANGOLA.JPG
456 ms
I410-FUNDOPAVCIDADELAAUDIUMSITE.JPG
528 ms
I411-NOVOXBANCO.JPG
564 ms
I406-VALSASSINAX05.JPG
522 ms
I412-MUSEUARRAIOLOS.JPG
529 ms
I389-AUDITORIOAUDIUMANGOLA.JPG
531 ms
I409-ETXBACKXNEWSL.JPG
597 ms
I395-AUREA.JPG
604 ms
I417-FACEBOOKXLOGO.JPG
606 ms
audium.png
607 ms
sk-nws-aderir.php
573 ms
__utm.gif
15 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
18 ms
k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff
24 ms
glyphicons-halflings-regular.woff
542 ms
audium.pt accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
audium.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
audium.pt SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Audium.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 Audium.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.
audium.pt
Open Graph description is not detected on the main page of AUDIUM. 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: