O2.PL o2 - Serce Internetu


o2.pl website information.

o2.pl website servers are located in Poland and are responding from following IP address 212.77.100.61. Check the full list of most visited websites located in Poland.

o2.pl domain name is registered by .PL top-level domain registry. See the other sites registred in .PL domain zone.

Following name servers are specified for o2.pl domain:

  • ns2.go2.pl
  • ns1.go2.pl

and probably website o2.pl is hosted by go2.pl web hosting company. Check the complete list of other most popular websites hosted by go2.pl hosting company.

According to Alexa traffic rank the highest website o2.pl position was 871 (in the world). The lowest Alexa rank position was 4021. Now website o2.pl ranked in Alexa database as number 2103 (in the world).

Website o2.pl Desktop speed measurement score (69/100) is better than the results of 50.07% of other sites shows that the page desktop performance can be improved.

o2.pl Mobile usability score (99/100) is better than the results of 87.11% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of o2.pl (50/100) is better than the results of 31.51% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Oct-23-2019 2,103511
Oct-22-2019 2,6141,407
Oct-21-2019 4,021-2,077
Oct-20-2019 1,944-267
Oct-19-2019 1,677843
Oct-18-2019 2,520-115
Oct-17-2019 2,405-476

Advertisement

o2.pl 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.


o2.pl 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.


request limit exceeded

o2.pl server information

Servers Location

o2.pl desktop page speed rank

Last tested: 2017-04-28


Desktop Speed Medium
69/100

o2.pl Desktop Speed Test Quick Summary


priority - 16 Optimize images

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

Optimize the following images to reduce their size by 158.7KiB (48% reduction).

Compressing https://i.wpimg.pl/668x445/d.wpimg.pl/1715301506--2022726984/policja.jpg could save 33.5KiB (49% reduction).
Compressing https://i.wpimg.pl/356x238/d.wpimg.pl/1172746374-1…-uchodzcy-festiwal.jpg could save 23.5KiB (50% reduction).
Compressing https://i.wpimg.pl/356x238/d.wpimg.pl/2020129655-251605432/aktorka.jpg could save 17.4KiB (49% reduction).
Compressing https://i.wpimg.pl/356x238/d.wpimg.pl/175723947--1431823755/bikini.jpg could save 11KiB (44% reduction).
Compressing https://i.wpimg.pl/176x117/d.wpimg.pl/1620123563-1504384061/maraton.jpg could save 7.5KiB (49% reduction).
Compressing https://i.wpimg.pl/176x117/d.wpimg.pl/967068180-1561867684/blizniaczki.jpg could save 6KiB (48% reduction).
Compressing https://i.wpimg.pl/176x117/d.wpimg.pl/549489371-324518893/cwiczenia-sen.jpg could save 5.6KiB (48% reduction).
Compressing https://i.wpimg.pl/176x117/d.wpimg.pl/1891944430-1…lotniskowiec-okret.JPG could save 5.5KiB (50% reduction).
Compressing https://i.wpimg.pl/176x117/d.wpimg.pl/1129729765-1…misiewicz-piotrkow.jpg could save 5.4KiB (48% reduction).
Compressing https://i.wpimg.pl/176x117/d.wpimg.pl/1783636888-1017582510/mozg.jpg could save 5.3KiB (46% reduction).
Compressing https://i.wpimg.pl/176x117/d.wpimg.pl/1113259712--713429713/zajawka-o2.jpeg could save 5.2KiB (48% reduction).
Compressing https://i.wpimg.pl/132x89/d.wpimg.pl/1663303367-80…port-miniatury-do.jpeg could save 4.1KiB (49% reduction).
Compressing https://i.wpimg.pl/132x89/d.wpimg.pl/1252582401--4…mport-miniatury-do.jpg could save 4KiB (48% reduction).
Compressing https://i.wpimg.pl/132x89/d.wpimg.pl/2077089828--2…port-miniatury-do.jpeg could save 3.5KiB (48% reduction).
Compressing https://i.wpimg.pl/132x89/d.wpimg.pl/1199569896--1…port-miniatury-do.jpeg could save 3.5KiB (47% reduction).
Compressing https://i.wpimg.pl/132x89/d.wpimg.pl/2112047739--1…mport-miniatury-do.png could save 3.4KiB (47% reduction).
Compressing https://i.wpimg.pl/176x117/d.wpimg.pl/1654406120-667543077/gajda.jpg could save 3.3KiB (44% reduction).
Compressing https://i.wpimg.pl/132x89/d.wpimg.pl/268541600--19…mport-miniatury-do.jpg could save 2.6KiB (48% reduction).
Compressing https://i.wpimg.pl/115x115/d.wpimg.pl/1870667575-1…0476/przetakiewicz.jpg could save 2.6KiB (46% reduction).
Compressing https://i.wpimg.pl/176x117/d.wpimg.pl/1749681311--…/rakieta-minuteman.jpg could save 2.3KiB (49% reduction).
Compressing https://i.wpimg.pl/115x115/d.wpimg.pl/1638587521-3…onislaw-komorowski.jpg could save 2.3KiB (44% reduction).
Compressing https://owabgxis.wp.pl/Uk0vQm94LzIwMTctMDQvcnAvMTE…lyb3draS0xMzJ4ODkuanBn could save 1.3KiB (34% reduction).

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

Your page has 3 blocking script resources and 1 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://adv.wp.pl/RM/Box/c/b/inline/inline-o2_gaf.js
https://a.wpimg.pl/a/i/stg/wpjslib-core.js
https://www.o2.pl/static/desktop.js

Optimize CSS Delivery of the following:

https://www.o2.pl/static/desktop.css

priority - 7 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://o2.pl/
http://www.o2.pl/
https://www.o2.pl/

priority - 5 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://api.o2.pl/auth/settings (expiration not specified)
https://api.o2.pl/stat/v1/viewers/quiz (expiration not specified)
https://fntajkb.wp.pl/Z2FmLmpzP3Jlc3BvbnNlVmVyc2lv…Zsc3RhdGlkPWYmYmN2PTI= (expiration not specified)
https://open.fm/api/api-ext/v2/channels/109/medium.json (expiration not specified)
https://www.o2.pl/static/desktop.css (expiration not specified)
https://www.o2.pl/static/desktop.js (expiration not specified)
https://a.wpimg.pl/a/i/stg/wpjslib-core.js (5 minutes)
https://adv.wp.pl/RM/Box/c/b/inline/inline-o2_gaf.js (15 minutes)
https://connect.facebook.net/pl_PL/sdk.js (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 4 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 2% of the final above-the-fold content could be rendered with the full HTML response.

o2.pl Desktop Resources

Total Resources102
Number of Hosts36
Static Resources34
JavaScript Resources32
CSS Resources1

o2.pl Desktop Resource Breakdown

o2.pl mobile page speed rank

Last tested: 2017-04-27


Mobile Speed Bad
50/100

o2.pl Mobile Speed Test Quick Summary


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

Your page has 3 blocking script resources and 1 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://adv.wp.pl/RM/Box/c/b/inline/inline-o2_mobile.js
https://a.wpimg.pl/a/i/stg/wpjslib-core.js
https://www.o2.pl/static/mobile.js

Optimize CSS Delivery of the following:

https://www.o2.pl/static/mobile.css

priority - 26 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://o2.pl/
http://www.o2.pl/
https://www.o2.pl/

priority - 10 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://fntajkb.wp.pl/Z2FmLmpzP3Jlc3BvbnNlVmVyc2lv…lsZV9vMl94MTcmYmN2PTI= (expiration not specified)
https://fntajkb.wp.pl/Z2FmLmpzP3Jlc3BvbnNlVmVyc2lv…N0eXBlPWluZGV4JmJjdj0y (expiration not specified)
https://www.o2.pl/static/13326f253e09db48d40d91aadac2e4dd.png (expiration not specified)
https://www.o2.pl/static/2b2505beb6d49e4b6e2e545b6c54af19.woff2 (expiration not specified)
https://www.o2.pl/static/mobile.css (expiration not specified)
https://www.o2.pl/static/mobile.js (expiration not specified)
https://www.o2.pl/v1/grid/2 (expiration not specified)
https://www.o2.pl/v1/grid/3 (expiration not specified)
https://www.o2.pl/v1/grid/4 (expiration not specified)
https://a.wpimg.pl/a/i/stg/wpjslib-core.js (5 minutes)
https://adv.wp.pl/RM/Box/c/b/inline/inline-o2_mobile.js (15 minutes)
https://connect.facebook.net/pl_PL/sdk.js (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 9 Optimize images

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

Optimize the following images to reduce their size by 88.2KiB (48% reduction).

Compressing https://i.wpimg.pl/408x275/d.wpimg.pl/2058408589-1…03076/dziewczynki.jpeg could save 30.6KiB (49% reduction).
Compressing https://i.wpimg.pl/408x275/d.wpimg.pl/1626695309-778345208/zajawka-o2.jpeg could save 11.7KiB (47% reduction).
Compressing https://i.wpimg.pl/408x275/d.wpimg.pl/1749681311--…/rakieta-minuteman.jpg could save 8.7KiB (49% reduction).
Compressing https://i.wpimg.pl/220x147/d.wpimg.pl/1779206996--374961553/smaki-zycia.jpg could save 8.5KiB (48% reduction).
Compressing https://i.wpimg.pl/204x137/d.wpimg.pl/2004328283--2079873391/znaki.png could save 8.4KiB (50% reduction).
Compressing https://i.wpimg.pl/204x137/d.wpimg.pl/385416438--9…831/jimena-sanchez.jpg could save 8.2KiB (47% reduction).
Compressing https://i.wpimg.pl/204x137/d.wpimg.pl/227295611-1607853301/kupa.jpg could save 5.8KiB (46% reduction).
Compressing https://i.wpimg.pl/96x64/d.wpimg.pl/1848368467-286…tnisko-w-bagdadzie.jpg could save 1.7KiB (46% reduction).
Compressing https://i.wpimg.pl/96x64/d.wpimg.pl/608308020-146505406/mri.png could save 1.7KiB (44% reduction).
Compressing https://i.wpimg.pl/96x64/d.wpimg.pl/1611118857--60…uro-ochrony-rzadu.jpeg could save 1.5KiB (46% reduction).
Compressing https://i.wpimg.pl/96x64/d.wpimg.pl/1626695309-778345208/zajawka-o2.jpeg could save 1.4KiB (45% 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 12% of the final above-the-fold content could be rendered with the full HTML response.

o2.pl Mobile Resources

Total Resources81
Number of Hosts32
Static Resources24
JavaScript Resources23
CSS Resources1

o2.pl Mobile Resource Breakdown

o2.pl mobile page usability

Last tested: 2017-04-27


Mobile Usability Good
99/100

o2.pl 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.

The tap target <a href="http://onas.wp.pl">O nas</a> and 1 others are close to other tap targets.

o2.pl Mobile Resources

Total Resources81
Number of Hosts32
Static Resources24
JavaScript Resources23
CSS Resources1

o2.pl Mobile Resource Breakdown

o2.pl similar domains

Similar domains:
www.o2.com
www.o2.net
www.o2.org
www.o2.info
www.o2.biz
www.o2.us
www.o2.mobi
www.2.pl
www.o2.pl
www.i2.pl
www.oi2.pl
www.io2.pl
www.k2.pl
www.ok2.pl
www.ko2.pl
www.l2.pl
www.ol2.pl
www.lo2.pl
www.p2.pl
www.op2.pl
www.po2.pl
www.o.pl

o2.pl 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.


o2.pl 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.