7.2 sec in total
503 ms
5 sec
1.7 sec
Welcome to altice.pt homepage info - get ready to check Altice best content for Portugal right away, or after learning these important things about altice.pt
Atuamos de Portugal para o Mundo, investindo e intervindo em quatro dimensões fundamentais: Pessoas, Tecnologia, Inovação e Sustentabilidade.
Visit altice.ptWe analyzed Altice.pt page load time and found that the first response time was 503 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
altice.pt performance score
name
value
score
weighting
Value19.0 s
0/100
10%
Value25.3 s
0/100
25%
Value21.8 s
0/100
10%
Value910 ms
31/100
30%
Value0.002
100/100
15%
Value41.4 s
0/100
10%
503 ms
369 ms
550 ms
53 ms
552 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 57% of them (50 requests) were addressed to the original Altice.pt, 33% (29 requests) were made to Conteudos.altice.pt and 3% (3 requests) were made to Webcare.byside.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Conteudos.altice.pt.
Page size can be reduced by 2.6 MB (42%)
6.3 MB
3.7 MB
In fact, the total size of Altice.pt main page is 6.3 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. 60% of websites need less resources to load. Javascripts take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 52.4 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 8.5 kB, which is 12% 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 52.4 kB or 76% of the original size.
Potential reduce by 69.8 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. Altice images are well optimized though.
Potential reduce by 2.1 MB
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 2.1 MB or 72% of the original size.
Potential reduce by 417.0 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. Altice.pt needs all CSS files to be minified and compressed as it can save up to 417.0 kB or 87% of the original size.
Number of requests can be reduced by 55 (68%)
81
26
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Altice. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.altice.pt
503 ms
pt
369 ms
QuantcastTag_Universal.js
550 ms
gtm.js
53 ms
ISites.Configurations.js
552 ms
searchv15.css
395 ms
initstrings.js
506 ms
init.js
922 ms
ScriptResource.axd
515 ms
blank.js
418 ms
ScriptResource.axd
425 ms
sp.res.js
576 ms
sp.runtime.js
775 ms
sp.init.js
606 ms
sp.search.js
688 ms
clientrenderer.js
608 ms
srch.resources.js
756 ms
search.clientcontrols.js
972 ms
search.cbs.js
701 ms
altice.css
2154 ms
jquery-3.5.1.min.js
750 ms
system.js
752 ms
system.config.js
554 ms
brandlib.js
948 ms
altice.js
647 ms
postMessagesHelper.js
659 ms
ISites.js
752 ms
functions.js
982 ms
functionsv2.js
854 ms
ISites.Utils.js
856 ms
ISites.Search.js
858 ms
menuv5.js
1223 ms
ISites.Configurations.Search.js
976 ms
weglot.min.js
39 ms
ISites.WegLot.js
963 ms
ISites.WegLot.Altice.js
1047 ms
WebResource.axd
782 ms
normalize.css
709 ms
default.css
863 ms
main.css
880 ms
swiper-bundle.min.css
805 ms
swiper-bundle.min.js
1057 ms
main.js
1210 ms
system-polyfills.js
133 ms
banner-1.jpg
925 ms
banner-1-mobile.jpg
322 ms
bars.png
125 ms
slide-operate-1.jpg
282 ms
slide-operate-2.jpg
555 ms
slide-operate-3.jpg
571 ms
slide-operate-4.jpg
558 ms
cyan-img.jpg
559 ms
cyan-img-mobile.jpg
561 ms
yellow-img.jpg
651 ms
yellow-img-mobile.jpg
741 ms
green-img.jpg
743 ms
green-img-mobile.jpg
766 ms
blue-img.jpg
753 ms
blue-img-mobile.jpg
839 ms
Montserrat-Light.ttf
434 ms
Montserrat-Regular.ttf
433 ms
Montserrat-SemiBold.ttf
421 ms
menuv5.config.js
119 ms
cyan-hover.png
779 ms
yellow-hover.png
791 ms
blue-hover.png
789 ms
green-hover.png
801 ms
icons-meo.ttf
220 ms
strings.js
1028 ms
searchcenterurl
873 ms
ProcessQuery
1124 ms
item_colunas.js
828 ms
group_content.js
854 ms
control_colunas.js
846 ms
GetTaxonomy
644 ms
GetTaxonomy
671 ms
byside_webcare.js
661 ms
main-menu-v5-ISites.js
207 ms
473 ms
action.php
312 ms
customstrings.js
98 ms
displaytemplateshelper.js
207 ms
react.production.min.js
107 ms
react-dom.production.min.js
313 ms
core.js
524 ms
columnsApp.min.js
119 ms
st.php
128 ms
altice.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-*] attributes do not have valid values
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
Links do not have a discernible name
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.
altice.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
Page has valid source maps
altice.pt SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Altice.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 Altice.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.
altice.pt
Open Graph data is detected on the main page of Altice. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: