altice.pt website information.
altice.pt domain name is registered by .PT top-level domain registry. See the other sites registred in .PT domain zone.
No name server records were found.
and probably website altice.pt is hosted by GOOGLE - Google LLC, US web hosting company. Check the complete list of other most popular websites hosted by GOOGLE - Google LLC, US hosting company.
According to Alexa traffic rank the highest website altice.pt position was 22446 (in the world). The lowest Alexa rank position was 990358. Now website altice.pt ranked in Alexa database as number 186235 (in the world).
Website altice.pt Desktop speed measurement score (45/100) is better than the results of 19.01% of other sites shows that the page desktop performance can be improved.
altice.pt Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of altice.pt (28/100) is better than the results of 8.55% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
Date | Rank | Change |
---|---|---|
Nov-16-2024 | 186,235 | 11,025 |
Nov-15-2024 | 197,260 | -4,574 |
Nov-14-2024 | 192,686 | 58,092 |
Nov-13-2024 | 250,778 | 0 |
Nov-12-2024 | 250,778 | 0 |
Nov-11-2024 | 250,778 | 0 |
Nov-10-2024 | 250,778 | -4,362 |
Advertisement
altice.pt Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
altice.pt whois
WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.
altice.pt server information
Servers Location
IP Address |
---|
Country |
---|
altice.pt desktop page speed rank
Last tested: 2018-05-21
altice.pt Desktop Speed Test Quick Summary
priority - 64 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 626.9KiB (39% reduction).
Compressing https://www.telecom.pt/SiteCollectionImages/homepa…ldo-sofia-1580x580.jpg could save 173.5KiB (75% reduction).
Compressing and resizing https://www.telecom.pt/SiteCollectionImages/homepa…estaque_historia_L.JPG could save 146.2KiB (67% reduction).
Compressing https://www.telecom.pt/en-us/PublishingImages/Telecom_1580_580.png could save 70.2KiB (12% reduction).
Compressing https://www.telecom.pt/SITECOLLECTIONIMAGES/MEDIA/…G?width=450&height=271 could save 27.5KiB (11% reduction).
Compressing https://www.telecom.pt/Style%20Library/Telecom/ima…favicon_alt.ico?rev=23 could save 1KiB (64% reduction).
Compressing https://www.telecom.pt/Style%20Library/Telecom/images/seta_brand.png could save 875B (87% reduction).
Compressing https://www.telecom.pt/Style%20Library/Telecom/images/social-icons.png could save 715B (24% reduction).
Compressing https://www.telecom.pt/SiteCollectionImages/logo-altice-white.png could save 618B (19% reduction).
Compressing https://www.telecom.pt/SiteCollectionImages/altice_logo_black.png could save 575B (15% reduction).
Compressing https://www.telecom.pt/SiteCollectionImages/altice_logo_black.png?rev=23 could save 575B (15% reduction).
priority - 26 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://www.telecom.pt/Style%20Library/Telecom/css/normalize.min.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/ima…favicon_alt.ico?rev=23 (24 hours)
https://www.telecom.pt/SITECOLLECTIONIMAGES/MEDIA/…G?width=450&height=271 (24 hours)
https://www.telecom.pt/SITECOLLECTIONIMAGES/MEDIA/…G?width=450&height=271 (24 hours)
https://www.telecom.pt/SITECOLLECTIONIMAGES/MEDIA/…G?width=450&height=271 (24 hours)
https://www.telecom.pt/SiteCollectionImages/altice_logo_black.png (24 hours)
https://www.telecom.pt/SiteCollectionImages/altice_logo_black.png?rev=23 (24 hours)
https://www.telecom.pt/SiteCollectionImages/homepa…estaque_historia_L.JPG (24 hours)
https://www.telecom.pt/SiteCollectionImages/homepa…elecom_1580_580_EN.jpg (24 hours)
https://www.telecom.pt/SiteCollectionImages/homepa…ldo-sofia-1580x580.jpg (24 hours)
https://www.telecom.pt/SiteCollectionImages/logo-altice-white.png (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/default.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/fix.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/footer.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/header.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/print.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/theme.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/images/seta_brand.png (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/images/social-icons.png (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/images/sprite-logos-v2.png (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/brandlib.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…ies.js?_=1526907602493 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…rchAutoComplete.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/Telecom.search.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…elecom.validate.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/captcha.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…template.helper.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery-ui.min.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…ces-2014.02.min.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery.cookie.js (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery.cookie.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…gelayout.helper.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…taxonomy.helper.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…m.configuration.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/telecom.helper.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/translator.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/fileinput.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/functions.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/grid.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/jquery-1.11.2.min.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/jquery.mobile.min.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/lemon.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/main.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/regua.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/slick.min.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/en-US/Thema…yles/pagelayouts15.css (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/en-us/PublishingImages/Telecom_1580_580.png (24 hours)
https://www.telecom.pt/style%20library/Telecom/js/…der.js?_=1526907602494 (24 hours)
https://www.telecom.pt/style%20library/telecom/js/header.js (24 hours)
https://www.telecom.pt/style%20library/telecom/js/html5.js (24 hours)
https://www.telecom.pt/style%20library/telecom/js/meolib.js (24 hours)
priority - 18 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 52 blocking script resources and 9 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
https://www.telecom.pt/style%20library/telecom/js/html5.js
https://www.telecom.pt/style%20library/telecom/js/meolib.js
https://www.telecom.pt/Style%20Library/Telecom/js/brandlib.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/jquery-1.11.2.min.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/slick.min.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/fileinput.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…m.configuration.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…taxonomy.helper.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/telecom.helper.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…ces-2014.02.min.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/translator.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery.cookie.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery-ui.min.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…template.helper.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/captcha.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…elecom.validate.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/Telecom.search.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…gelayout.helper.js?v10
https://www.telecom.pt/ScriptResource.axd?d=B8AZ6_…zk0&t=ffffffff805766b3
https://www.telecom.pt/_layouts/15/blank.js?rev=Za…VwykPO9g8hq%2F8A%3D%3D
https://www.telecom.pt/ScriptResource.axd?d=dxZ2wp…SP0&t=ffffffff805766b3
https://www.telecom.pt/_layouts/15/sp.init.js?rev=…l5gbORaLtf7kxULQ%3D%3D
https://www.telecom.pt/_layouts/15/clientrenderer.…ATEiOxN90BeB5Hzw%3D%3D
https://www.telecom.pt/_layouts/15/ScriptResx.ashx…WaZD2DDDiSAgLxjQ%3D%3D
https://www.telecom.pt/_layouts/15/search.clientco…OhdMDlyCSUMQPtrg%3D%3D
https://www.telecom.pt/_layouts/15/search.cbs.js?r…QhNKgWxVFmcqr5dQ%3D%3D
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_layouts/15/ScriptResx.ashx…Bn40LJVP%2BqfgdQ%3D%3D
https://www.telecom.pt/_layouts/15/sp.ui.dialog.js…aaiXSb7ldu2zd6QQ%3D%3D
https://www.telecom.pt/_layouts/15/sp.runtime.js?r…JoaxlIRdwUeg4WEg%3D%3D
https://www.telecom.pt/_layouts/15/sp.js?rev=0u73UVrnqhFPlqac45wInQ%3D%3D
https://www.telecom.pt/_layouts/15/sp.taxonomy.js?…IPJsJ7ns7%2FTnog%3D%3D
https://www.telecom.pt/Style%20Library/Telecom/js/jquery.mobile.min.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/lemon.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/regua.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/functions.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/grid.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…rchAutoComplete.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/main.js?v10
https://www.telecom.pt/style%20library/telecom/js/header.js
https://js.sapo.pt/SAPOWebAnalytics/
https://www.telecom.pt/WebResource.axd?d=F7OBVnFrN…1&t=635588618815688065
https://www.telecom.pt/_layouts/15/blank.js?rev=Za…VwykPO9g8hq%2F8A%3D%3D
Optimize CSS Delivery of the following:
https://www.telecom.pt/_layouts/15/1033/styles/The…KbtAsTIA4uW3YOqA%3D%3D
https://www.telecom.pt/_layouts/15/1033/styles/The…3eURu3ZS2Wsbpf2w%3D%3D
https://www.telecom.pt/Style%20Library/Telecom/css/normalize.min.css?v10
https://www.telecom.pt/Style%20Library/Telecom/css/default.css?v10
https://www.telecom.pt/Style%20Library/Telecom/css/fix.css?v10
https://www.telecom.pt/Style%20Library/Telecom/css/theme.css?v10
https://www.telecom.pt/Style%20Library/Telecom/css/header.css?v10
https://www.telecom.pt/Style%20Library/Telecom/css/footer.css?v10
priority - 13 Avoid landing page redirects
Your page has 4 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
http://www.telecom.pt/
https://www.telecom.pt/
https://www.telecom.pt/Paginas/VariationRoot.aspx
https://www.telecom.pt/en-us
priority - 7 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 72.7KiB (36% reduction).
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/brandlib.js?v10 could save 5.4KiB (18% reduction) after compression.
Minifying https://www.telecom.pt/style%20library/Telecom/js/…der.js?_=1526907602494 could save 4.5KiB (39% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/dev/telecom.helper.js?v10 could save 3.1KiB (31% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/functions.js?v10 could save 2.6KiB (29% reduction) after compression.
Minifying https://www.telecom.pt/style%20library/telecom/js/meolib.js could save 2KiB (16% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…taxonomy.helper.js?v10 could save 1.9KiB (70% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/regua.js?v10 could save 1.3KiB (41% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/main.js?v10 could save 1KiB (42% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/lemon.js?v10 could save 797B (37% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…ies.js?_=1526907602493 could save 674B (36% reduction) after compression.
Minifying https://www.telecom.pt/style%20library/telecom/js/header.js could save 643B (20% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 641B (20% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/dev/captcha.js?v10 could save 624B (32% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery.cookie.js could save 563B (42% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery.cookie.js?v10 could save 563B (42% reduction) after compression.
Minifying https://www.telecom.pt/WebResource.axd?d=F7OBVnFrN…1&t=635588618815688065 could save 525B (12% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 510B (21% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 490B (17% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…gelayout.helper.js?v10 could save 469B (21% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…elecom.validate.js?v10 could save 448B (32% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 397B (28% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 383B (26% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 379B (30% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…template.helper.js?v10 could save 365B (17% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/dev/Telecom.search.js?v10 could save 341B (24% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 290B (25% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 221B (25% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…m.configuration.js?v10 could save 146B (20% reduction) after compression.
priority - 2 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 22.8KiB (20% reduction).
Minifying https://www.telecom.pt/_layouts/15/1033/styles/The…KbtAsTIA4uW3YOqA%3D%3D could save 5.9KiB (14% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/css/fix.css?v10 could save 2.2KiB (29% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/css/theme.css?v10 could save 987B (35% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/css/header.css?v10 could save 905B (13% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/css/footer.css?v10 could save 170B (16% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/en-US/Thema…yles/pagelayouts15.css could save 111B (13% reduction) after compression.
priority - 2 Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 0 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 630B (44% reduction).
Compressing https://www.telecom.pt/_vti_bin/Webs.asmx could save 195B (45% reduction).
altice.pt Desktop Resources
Total Resources | 102 |
Number of Hosts | 5 |
Static Resources | 83 |
JavaScript Resources | 62 |
CSS Resources | 10 |
altice.pt Desktop Resource Breakdown
altice.pt mobile page speed rank
Last tested: 2018-05-21
altice.pt Mobile Speed Test Quick Summary
priority - 83 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 811.5KiB (46% reduction).
Compressing https://www.telecom.pt/SiteCollectionImages/homepa…elecom_1580_580_EN.jpg could save 205.1KiB (77% reduction).
Compressing https://www.telecom.pt/SiteCollectionImages/homepa…ldo-sofia-1580x580.jpg could save 173.5KiB (75% reduction).
Compressing https://www.telecom.pt/en-us/PublishingImages/Telecom_1580_580.png could save 70.2KiB (12% reduction).
Compressing https://www.telecom.pt/SiteCollectionImages/homepa…Telecom_424_375_EN.jpg could save 63.2KiB (74% reduction).
Compressing https://www.telecom.pt/SiteCollectionImages/homepa…aldo-sofia-414x375.jpg could save 62.2KiB (74% reduction).
Compressing https://www.telecom.pt/SITECOLLECTIONIMAGES/MEDIA/…G?width=450&height=271 could save 27.5KiB (11% reduction).
Compressing https://www.telecom.pt/Style%20Library/Telecom/ima…favicon_alt.ico?rev=23 could save 1KiB (64% reduction).
Compressing https://www.telecom.pt/Style%20Library/Telecom/images/seta_brand.png could save 875B (87% reduction).
Compressing https://www.telecom.pt/Style%20Library/Telecom/images/social-icons.png could save 715B (24% reduction).
Compressing https://www.telecom.pt/SiteCollectionImages/logo-altice-white.png could save 618B (19% reduction).
Compressing https://www.telecom.pt/SiteCollectionImages/altice_logo_black.png could save 575B (15% reduction).
Compressing https://www.telecom.pt/SiteCollectionImages/altice_logo_black.png?rev=23 could save 575B (15% reduction).
priority - 72 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 52 blocking script resources and 9 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
https://www.telecom.pt/style%20library/telecom/js/html5.js
https://www.telecom.pt/style%20library/telecom/js/meolib.js
https://www.telecom.pt/Style%20Library/Telecom/js/brandlib.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/jquery-1.11.2.min.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/slick.min.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/fileinput.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…m.configuration.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…taxonomy.helper.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/telecom.helper.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…ces-2014.02.min.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/translator.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery.cookie.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery-ui.min.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…template.helper.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/captcha.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…elecom.validate.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/dev/Telecom.search.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…gelayout.helper.js?v10
https://www.telecom.pt/ScriptResource.axd?d=B8AZ6_…zk0&t=ffffffff805766b3
https://www.telecom.pt/_layouts/15/blank.js?rev=Za…VwykPO9g8hq%2F8A%3D%3D
https://www.telecom.pt/ScriptResource.axd?d=dxZ2wp…SP0&t=ffffffff805766b3
https://www.telecom.pt/_layouts/15/sp.init.js?rev=…l5gbORaLtf7kxULQ%3D%3D
https://www.telecom.pt/_layouts/15/clientrenderer.…ATEiOxN90BeB5Hzw%3D%3D
https://www.telecom.pt/_layouts/15/ScriptResx.ashx…WaZD2DDDiSAgLxjQ%3D%3D
https://www.telecom.pt/_layouts/15/search.clientco…OhdMDlyCSUMQPtrg%3D%3D
https://www.telecom.pt/_layouts/15/search.cbs.js?r…QhNKgWxVFmcqr5dQ%3D%3D
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000
https://www.telecom.pt/_layouts/15/ScriptResx.ashx…Bn40LJVP%2BqfgdQ%3D%3D
https://www.telecom.pt/_layouts/15/sp.ui.dialog.js…aaiXSb7ldu2zd6QQ%3D%3D
https://www.telecom.pt/_layouts/15/sp.runtime.js?r…JoaxlIRdwUeg4WEg%3D%3D
https://www.telecom.pt/_layouts/15/sp.js?rev=0u73UVrnqhFPlqac45wInQ%3D%3D
https://www.telecom.pt/_layouts/15/sp.taxonomy.js?…IPJsJ7ns7%2FTnog%3D%3D
https://www.telecom.pt/Style%20Library/Telecom/js/jquery.mobile.min.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/lemon.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/regua.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/functions.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/grid.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/…rchAutoComplete.js?v10
https://www.telecom.pt/Style%20Library/Telecom/js/main.js?v10
https://www.telecom.pt/style%20library/telecom/js/header.js
https://js.sapo.pt/SAPOWebAnalytics/
https://www.telecom.pt/WebResource.axd?d=F7OBVnFrN…1&t=635588618815688065
https://www.telecom.pt/_layouts/15/blank.js?rev=Za…VwykPO9g8hq%2F8A%3D%3D
Optimize CSS Delivery of the following:
https://www.telecom.pt/_layouts/15/1033/styles/The…KbtAsTIA4uW3YOqA%3D%3D
https://www.telecom.pt/_layouts/15/1033/styles/The…3eURu3ZS2Wsbpf2w%3D%3D
https://www.telecom.pt/Style%20Library/Telecom/css/normalize.min.css?v10
https://www.telecom.pt/Style%20Library/Telecom/css/default.css?v10
https://www.telecom.pt/Style%20Library/Telecom/css/fix.css?v10
https://www.telecom.pt/Style%20Library/Telecom/css/theme.css?v10
https://www.telecom.pt/Style%20Library/Telecom/css/header.css?v10
https://www.telecom.pt/Style%20Library/Telecom/css/footer.css?v10
priority - 45 Avoid landing page redirects
Your page has 4 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
http://www.telecom.pt/
https://www.telecom.pt/
https://www.telecom.pt/Paginas/VariationRoot.aspx
https://www.telecom.pt/en-us
priority - 41 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://www.telecom.pt/SITECOLLECTIONIMAGES/MEDIA/…G?width=450&height=271 (24 hours)
https://www.telecom.pt/SITECOLLECTIONIMAGES/MEDIA/…G?width=450&height=271 (24 hours)
https://www.telecom.pt/SITECOLLECTIONIMAGES/MEDIA/…G?width=450&height=271 (24 hours)
https://www.telecom.pt/SiteCollectionImages/altice_logo_black.png (24 hours)
https://www.telecom.pt/SiteCollectionImages/altice_logo_black.png?rev=23 (24 hours)
https://www.telecom.pt/SiteCollectionImages/homepa…estaque_historia_L.JPG (24 hours)
https://www.telecom.pt/SiteCollectionImages/homepa…elecom_1580_580_EN.jpg (24 hours)
https://www.telecom.pt/SiteCollectionImages/homepa…Telecom_424_375_EN.jpg (24 hours)
https://www.telecom.pt/SiteCollectionImages/homepa…ldo-sofia-1580x580.jpg (24 hours)
https://www.telecom.pt/SiteCollectionImages/homepa…aldo-sofia-414x375.jpg (24 hours)
https://www.telecom.pt/SiteCollectionImages/logo-altice-white.png (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/default.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/fix.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/footer.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/header.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/normalize.min.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/print.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/css/theme.css?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/ima…favicon_alt.ico?rev=23 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/images/seta_brand.png (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/images/social-icons.png (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/images/sprite-logos-v2.png (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/brandlib.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…ies.js?_=1526907618174 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…rchAutoComplete.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/Telecom.search.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…elecom.validate.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/captcha.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…template.helper.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery-ui.min.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…ces-2014.02.min.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery.cookie.js (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery.cookie.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…gelayout.helper.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…taxonomy.helper.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/…m.configuration.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/telecom.helper.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/dev/translator.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/fileinput.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/functions.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/grid.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/jquery-1.11.2.min.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/jquery.mobile.min.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/lemon.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/main.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/regua.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/Telecom/js/slick.min.js?v10 (24 hours)
https://www.telecom.pt/Style%20Library/en-US/Thema…yles/pagelayouts15.css (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 (24 hours)
https://www.telecom.pt/en-us/PublishingImages/Telecom_1580_580.png (24 hours)
https://www.telecom.pt/style%20library/Telecom/js/…der.js?_=1526907618175 (24 hours)
https://www.telecom.pt/style%20library/telecom/js/header.js (24 hours)
https://www.telecom.pt/style%20library/telecom/js/html5.js (24 hours)
https://www.telecom.pt/style%20library/telecom/js/meolib.js (24 hours)
priority - 8 Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 7 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 72.7KiB (36% reduction).
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/brandlib.js?v10 could save 5.4KiB (18% reduction) after compression.
Minifying https://www.telecom.pt/style%20library/Telecom/js/…der.js?_=1526907618175 could save 4.5KiB (39% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/dev/telecom.helper.js?v10 could save 3.1KiB (31% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/functions.js?v10 could save 2.6KiB (29% reduction) after compression.
Minifying https://www.telecom.pt/style%20library/telecom/js/meolib.js could save 2KiB (16% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…taxonomy.helper.js?v10 could save 1.9KiB (70% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/regua.js?v10 could save 1.3KiB (41% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/main.js?v10 could save 1KiB (42% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/lemon.js?v10 could save 797B (37% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…ies.js?_=1526907618174 could save 674B (36% reduction) after compression.
Minifying https://www.telecom.pt/style%20library/telecom/js/header.js could save 643B (20% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 641B (20% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/dev/captcha.js?v10 could save 624B (32% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery.cookie.js could save 563B (42% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/dev/jquery.cookie.js?v10 could save 563B (42% reduction) after compression.
Minifying https://www.telecom.pt/WebResource.axd?d=F7OBVnFrN…1&t=635588618815688065 could save 525B (12% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 510B (21% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 490B (17% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…gelayout.helper.js?v10 could save 469B (21% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…elecom.validate.js?v10 could save 448B (32% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 397B (28% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 383B (26% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 379B (30% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…template.helper.js?v10 could save 365B (17% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/dev/Telecom.search.js?v10 could save 341B (24% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 290B (25% reduction) after compression.
Minifying https://www.telecom.pt/_catalogs/masterpage/displa…g=1384$$15.0.4867.1000 could save 221B (25% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/js/…m.configuration.js?v10 could save 146B (20% reduction) after compression.
priority - 2 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 22.8KiB (20% reduction).
Minifying https://www.telecom.pt/_layouts/15/1033/styles/The…KbtAsTIA4uW3YOqA%3D%3D could save 5.9KiB (14% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/css/fix.css?v10 could save 2.2KiB (29% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/css/theme.css?v10 could save 987B (35% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/css/header.css?v10 could save 905B (13% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/Telecom/css/footer.css?v10 could save 170B (16% reduction) after compression.
Minifying https://www.telecom.pt/Style%20Library/en-US/Thema…yles/pagelayouts15.css could save 111B (13% reduction) after compression.
priority - 0 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 630B (44% reduction).
Compressing https://www.telecom.pt/_vti_bin/Webs.asmx could save 195B (45% reduction).
altice.pt Mobile Resources
Total Resources | 104 |
Number of Hosts | 5 |
Static Resources | 85 |
JavaScript Resources | 62 |
CSS Resources | 10 |
altice.pt Mobile Resource Breakdown
altice.pt mobile page usability
Last tested: 2018-05-21
altice.pt Mobile Usability Test Quick Summary
priority - 0 Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<a href="https://www.fa…alticeportugal" class="social-icon-facebook"></a>
and 3 others are close to other tap targets.altice.pt similar domains
www.altice.net
www.altice.org
www.altice.info
www.altice.biz
www.altice.us
www.altice.mobi
www.ltice.pt
www.altice.pt
www.qltice.pt
www.aqltice.pt
www.qaltice.pt
www.wltice.pt
www.awltice.pt
www.waltice.pt
www.sltice.pt
www.asltice.pt
www.saltice.pt
www.zltice.pt
www.azltice.pt
www.zaltice.pt
www.atice.pt
www.aptice.pt
www.alptice.pt
www.apltice.pt
www.aotice.pt
www.alotice.pt
www.aoltice.pt
www.aktice.pt
www.alktice.pt
www.akltice.pt
www.alice.pt
www.alrice.pt
www.altrice.pt
www.alrtice.pt
www.alfice.pt
www.altfice.pt
www.alftice.pt
www.algice.pt
www.altgice.pt
www.algtice.pt
www.alyice.pt
www.altyice.pt
www.alytice.pt
www.altce.pt
www.altuce.pt
www.altiuce.pt
www.altuice.pt
www.altjce.pt
www.altijce.pt
www.altjice.pt
www.altkce.pt
www.altikce.pt
www.altkice.pt
www.altoce.pt
www.altioce.pt
www.altoice.pt
www.altie.pt
www.altixe.pt
www.alticxe.pt
www.altixce.pt
www.altide.pt
www.alticde.pt
www.altidce.pt
www.altife.pt
www.alticfe.pt
www.altifce.pt
www.altive.pt
www.alticve.pt
www.altivce.pt
www.altic.pt
www.alticw.pt
www.alticew.pt
www.alticwe.pt
www.altics.pt
www.altices.pt
www.alticse.pt
www.alticd.pt
www.alticed.pt
www.alticr.pt
www.alticer.pt
www.alticre.pt
altice.pt Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
altice.pt TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.