OPTIMUS.PT Há mais em NOS - NOS


optimus.pt website information.

optimus.pt domain name is registered by .PT top-level domain registry. See the other sites registred in .PT domain zone.

Following name servers are specified for optimus.pt domain:

  • ns1.novis.pt
  • ns2.novis.pt

and probably website optimus.pt is hosted by CLOUDFLARENET - Cloudflare, Inc., US web hosting company. Check the complete list of other most popular websites hosted by CLOUDFLARENET - Cloudflare, Inc., US hosting company.

According to Alexa traffic rank the highest website optimus.pt position was 150260 (in the world). The lowest Alexa rank position was 997638. Now website optimus.pt ranked in Alexa database as number 909363 (in the world).

Website optimus.pt Desktop speed measurement score (62/100) is better than the results of 38.44% of other sites shows that the page desktop performance can be improved.

optimus.pt Mobile usability score (98/100) is better than the results of 55.61% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of optimus.pt (63/100) is better than the results of 61.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-08-2024 909,363189
Nov-07-2024 909,552-24,945
Nov-06-2024 884,60739,018
Nov-05-2024 923,625-13,281
Nov-04-2024 910,344-5,505
Nov-03-2024 904,8394,669
Nov-02-2024 909,508-33,405

Advertisement

optimus.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.



optimus.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.


optimus.pt server information

Servers Location

IP Address
195.23.128.74
Country
Portugal
Region
Lisboa
City
Carnaxide

optimus.pt desktop page speed rank

Last tested: 2016-08-21


Desktop Speed Bad
62/100

optimus.pt Desktop Speed Test Quick Summary


priority - 36 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 346.8KiB (69% reduction).

Compressing http://cdn.nos.pt/www/d/js/jquery-ui.js could save 166.1KiB (73% reduction).
Compressing http://www.nos.pt/particulares/Pages/~/_layouts/15…mon/fonts/nos_font.svg could save 107.8KiB (66% reduction).
Compressing http://cdn.nos.pt/www/d/js/jquery.js could save 61.2KiB (65% reduction).
Compressing http://cdn.nos.pt/common/fonts/nosfont.svg could save 11.7KiB (66% reduction).

priority - 10 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 18 blocking script resources and 3 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:

http://www.nos.pt/_layouts/15/init.js?rev=0%2BjgcYFw8Xoj0N42kzP%2BcQ%3D%3D
http://www.nos.pt/_layouts/15/1033/initstrings.js?…wjnG3Tj9o5NrqHcg%3D%3D
http://www.nos.pt/_layouts/15/1033/strings.js?rev=…v1Os2YPb5X0keqRg%3D%3D
http://www.nos.pt/_layouts/15/ie55up.js?rev=0R4dbpInVlmjoVSw2Gglmw%3D%3D
http://www.nos.pt/ScriptResource.axd?d=u9cLITMUBSV…TS0&t=ffffffff805766b3
http://www.nos.pt/_layouts/15/blank.js?rev=ZaOXZEobVwykPO9g8hq%2F8A%3D%3D
http://www.nos.pt/ScriptResource.axd?d=44wLLD2ihcs…da0&t=ffffffff805766b3
http://cdn.nos.pt/www/d/js/jquery.js
http://www.nos.pt/_layouts/15/Armstrong/scripts/jayscript.min.js?v=14
http://www.nos.pt/_layouts/15/Armstrong/scripts/modernizr.custom.js
http://www.nos.pt/_layouts/15/Armstrong/scripts/login.js
http://webcare.byside.com/agent/byside_webcare.js
http://www.nos.pt/_layouts/15/Armstrong/scripts/GoogleTagManagerColor.js
http://www.nos.pt/WebResource.axd?d=KdlN13R_DErv-J…1&t=635589435571259667
http://www.nos.pt/_layouts/15/blank.js?rev=ZaOXZEobVwykPO9g8hq%2F8A%3D%3D
http://www.nos.pt/particulares/Documents/nostv/hww_js/hww_velocity.js
http://www.nos.pt/particulares/Documents/nostv/hww_js/lity.js
http://www.nos.pt/particulares/Documents/nostv/hww_js/hww_campaign.js

Optimize CSS Delivery of the following:

http://www.nos.pt/_layouts/15/Armstrong/css/screen.min.css?v=15
http://www.nos.pt/particulares/Documents/nostv/hww_css/lity.min.css
http://www.nos.pt/particulares/Documents/nostv/hww_css/hww_campaign.css

priority - 9 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://optimus.pt/
http://www.nos.pt/
http://www.nos.pt/Pages/default.aspx
http://www.nos.pt/particulares
http://www.nos.pt/particulares/Pages/home.aspx

priority - 6 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:

http://www.nos.pt/particulares/Pages/~/_layouts/15…n/fonts/fontcustom.css (expiration not specified)
http://www.nos.pt/particulares/Pages/~/_layouts/15…mon/fonts/nos_font.svg (expiration not specified)
http://www.nos.pt/particulares/Pages/~/_layouts/15…on/fonts/nos_font.woff (expiration not specified)
http://www.google-analytics.com/ga_exp.js?utmxkey=…utmxtime=1471735901783 (30 seconds)
http://www.googletagmanager.com/gtm.js?id=GTM-WXW542 (15 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
http://connect.facebook.net/en_US/fbds.js (20 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://cdn.nos.pt/common/fonts/nosfont.svg (5.5 hours)
http://cdn.nos.pt/common/img/nos.png (5.5 hours)
http://cdn.nos.pt/www/d/js/jquery-ui.js (5.5 hours)
http://cdn.nos.pt/www/d/js/jquery.js (5.5 hours)

priority - 2 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 22.6KiB (30% reduction).

Compressing http://www.nos.pt/particulares/PublishingImages/De…-agosto-2016/large.png could save 4.9KiB (26% reduction).
Compressing http://www.nos.pt/particulares/Documents/nostv/hww…s/hww_banner_01_bg.jpg could save 4KiB (16% reduction).
Compressing http://webcare.byside.com/files/289B72BD68/placeholders/x/18_close.png could save 2.7KiB (91% reduction).
Compressing http://www.nos.pt/particulares/Documents/nostv/hww_images/close.png could save 1.7KiB (42% reduction).
Compressing http://www.nos.pt/particulares/Documents/nostv/hww_images/hww_nos_tv.png could save 1.6KiB (55% reduction).
Compressing http://www.nos.pt/particulares/Documents/nostv/hww…s/hww_btn_appstore.png could save 1.5KiB (44% reduction).
Compressing http://www.nos.pt/particulares/Documents/nostv/hww…ww_btn_google_play.png could save 1.3KiB (32% reduction).
Compressing http://www.nos.pt/particulares/Documents/nostv/hww…ges/hww_btn_nos_tv.png could save 1.2KiB (52% reduction).
Compressing http://www.nos.pt/particulares/Documents/nostv/hww_images/mute.png could save 1.2KiB (22% reduction).
Compressing http://webcare.byside.com/files/289B72BD68/placeholders/x/close_mobile.png could save 1.1KiB (76% reduction).
Compressing http://www.nos.pt/_layouts/15/Armstrong/img/arrow_back.png could save 799B (76% reduction).
Compressing http://cdn.nos.pt/common/img/nos.png could save 686B (18% reduction).

priority - 0 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 1.8KiB (18% reduction).

Minifying http://webcare.byside.com/BWA289B72BD68/byside_contacts_src.js could save 739B (27% reduction) after compression.
Minifying http://www.nos.pt/particulares/Documents/nostv/hww_js/lity.js could save 587B (19% reduction) after compression.
Minifying http://www.nos.pt/WebResource.axd?d=KdlN13R_DErv-J…1&t=635589435571259667 could save 524B (12% reduction) after compression.

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 1.9KiB (11% reduction).

Minifying http://www.nos.pt/particulares/Pages/home.aspx could save 1.9KiB (11% reduction) after compression.

optimus.pt Desktop Resources

Total Resources146
Number of Hosts19
Static Resources55
JavaScript Resources42
CSS Resources6

optimus.pt Desktop Resource Breakdown

optimus.pt mobile page speed rank

Last tested: 2017-06-08


Mobile Speed Bad
63/100

optimus.pt Mobile Speed Test Quick Summary


priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 12 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Approximately 3% 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:

http://www.nos.pt/_layouts/15/init.js?rev=v4vAU%2Bw4fHSKHbcpMvHDqQ%3D%3D
http://www.nos.pt/ScriptResource.axd?d=u9cLITMUBSV…TS0&t=ffffffff805766b3
http://www.nos.pt/_layouts/15/blank.js?rev=ZaOXZEobVwykPO9g8hq%2F8A%3D%3D
http://cdn.nos.pt/www/d/js/jquery.js
http://www.nos.pt/_layouts/15/Armstrong/scripts/jayscript.min.js?v=14
http://www.nos.pt/_layouts/15/Armstrong/scripts/modernizr.custom.js
http://www.nos.pt/_layouts/15/Armstrong/scripts/login.js?v=1
http://webcare.byside.com/agent/byside_webcare.js
http://www.nos.pt/_layouts/15/Armstrong/scripts/GoogleTagManagerColor.js
http://www.nos.pt/_layouts/15/blank.js?rev=ZaOXZEobVwykPO9g8hq%2F8A%3D%3D
http://www.nos.pt/_layouts/15/Armstrong/scripts/responsive-carousel.min.js
http://www.nos.pt/_layouts/15/Armstrong/scripts/re…carousel.addons.min.js

Optimize CSS Delivery of the following:

http://www.nos.pt/_layouts/15/Armstrong/css/screen.min.css?v=15
http://nos.pt/_layouts/15/Armstrong/common/fonts/fontcustom.css

priority - 15 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 145.7KiB (37% reduction).

Compressing http://www.nos.pt/particulares/pacotes/vantagens-n…x1NPS/small-retina.png could save 77KiB (37% reduction).
Compressing http://www.nos.pt/particulares/PublishingImages/menu/Nos_telefone_drop.jpg could save 38.3KiB (73% reduction).
Compressing http://www.nos.pt/particulares/PublishingImages/De…i-marco2017/medium.png could save 8.2KiB (30% reduction).
Compressing http://www.nos.pt/particulares/PublishingImages/menu/NOS_Wi-Fi.png could save 7.7KiB (29% reduction).
Compressing http://www.nos.pt/particulares/PublishingImages/De…generico/33/medium.png could save 6.6KiB (12% reduction).
Compressing http://www.nos.pt/particulares/PublishingImages/menu/drop_nplay.png could save 6.4KiB (35% reduction).
Compressing http://www.nos.pt/_layouts/15/Armstrong/img/arrow_back.png could save 862B (82% reduction).
Compressing https://login.nos.pt/Content/icons/defaultprofilephoto.png could save 730B (35% reduction).

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.

Only about 20% of the final above-the-fold content could be rendered with the full HTML response.

priority - 6 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:

http://www.nos.pt/particulares/_layouts/15/NOS/loginservice.svc/GetInfoName (expiration not specified)
https://login.nos.pt/Content/icons/defaultprofilephoto.png (expiration not specified)
http://www.googletagmanager.com/gtm.js?id=GTM-WXW542 (15 minutes)
http://connect.facebook.net/en_US/fbds.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/1735496586702618?v=2.7.14 (20 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 2KiB (11% reduction).

Minifying http://www.nos.pt/ could save 2KiB (11% reduction) after compression.

priority - 0 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 695B (33% reduction).

Minifying http://connect.facebook.net/en_US/fbds.js could save 695B (33% reduction) after compression.

optimus.pt Mobile Resources

Total Resources72
Number of Hosts15
Static Resources38
JavaScript Resources29
CSS Resources3

optimus.pt Mobile Resource Breakdown

optimus.pt mobile page usability

Last tested: 2017-06-08


Mobile Usability Good
98/100

optimus.pt Mobile Usability Test Quick Summary


priority - 1 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.

The tap target <a href="http://www.nos…s/cookies.aspx">aqui</a> is close to 1 other tap targets.

The tap target <a href="/"></a> is close to 1 other tap targets.

The tap target <span class="icon2-menu ico…search__button"> and 1 others are close to other tap targets.

The tap target <span class="icon2-menu ico…search__button"> and 1 others are close to other tap targets.

The tap target <a href="#" class="noindex">INICIAR SESSÃO</a> and 1 others are close to other tap targets.

The tap target <input type="text" name="search-outside" class="nav-search__input"> is close to 1 other tap targets.

optimus.pt similar domains

Similar domains:
www.optimus.com
www.optimus.net
www.optimus.org
www.optimus.info
www.optimus.biz
www.optimus.us
www.optimus.mobi
www.ptimus.pt
www.optimus.pt
www.iptimus.pt
www.oiptimus.pt
www.ioptimus.pt
www.kptimus.pt
www.okptimus.pt
www.koptimus.pt
www.lptimus.pt
www.olptimus.pt
www.loptimus.pt
www.pptimus.pt
www.opptimus.pt
www.poptimus.pt
www.otimus.pt
www.ootimus.pt
www.opotimus.pt
www.ooptimus.pt
www.oltimus.pt
www.opltimus.pt
www.opimus.pt
www.oprimus.pt
www.optrimus.pt
www.oprtimus.pt
www.opfimus.pt
www.optfimus.pt
www.opftimus.pt
www.opgimus.pt
www.optgimus.pt
www.opgtimus.pt
www.opyimus.pt
www.optyimus.pt
www.opytimus.pt
www.optmus.pt
www.optumus.pt
www.optiumus.pt
www.optuimus.pt
www.optjmus.pt
www.optijmus.pt
www.optjimus.pt
www.optkmus.pt
www.optikmus.pt
www.optkimus.pt
www.optomus.pt
www.optiomus.pt
www.optoimus.pt
www.optius.pt
www.optinus.pt
www.optimnus.pt
www.optinmus.pt
www.optijus.pt
www.optimjus.pt
www.optikus.pt
www.optimkus.pt
www.optims.pt
www.optimys.pt
www.optimuys.pt
www.optimyus.pt
www.optimhs.pt
www.optimuhs.pt
www.optimhus.pt
www.optimjs.pt
www.optimujs.pt
www.optimis.pt
www.optimuis.pt
www.optimius.pt
www.optimu.pt
www.optimuw.pt
www.optimusw.pt
www.optimuws.pt
www.optimue.pt
www.optimuse.pt
www.optimues.pt
www.optimud.pt
www.optimusd.pt
www.optimuds.pt
www.optimuz.pt
www.optimusz.pt
www.optimuzs.pt
www.optimux.pt
www.optimusx.pt
www.optimuxs.pt
www.optimua.pt
www.optimusa.pt
www.optimuas.pt

optimus.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.


optimus.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.