su.pr website information.
su.pr domain name is registered by .PR top-level domain registry. See the other sites registred in .PR domain zone.
No name server records were found.
and probably website su.pr is hosted by WIKIMEDIA - Wikimedia Foundation Inc., US web hosting company. Check the complete list of other most popular websites hosted by WIKIMEDIA - Wikimedia Foundation Inc., US hosting company.
According to Alexa traffic rank the highest website su.pr position was 68165 (in the world). The lowest Alexa rank position was 908996. Now website su.pr ranked in Alexa database as number 168223 (in the world).
Website su.pr Desktop speed measurement score (69/100) is better than the results of 49.24% of other sites shows that the page desktop performance can be improved.
su.pr Mobile usability score (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of su.pr (67/100) is better than the results of 70.58% 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 |
|---|---|---|
| May-05-2024 | 168,223 | -1,734 |
| May-04-2024 | 166,489 | 4,691 |
| May-03-2024 | 171,180 | -3,267 |
| May-02-2024 | 167,913 | 1,076 |
| May-01-2024 | 168,989 | 760 |
| Apr-30-2024 | 169,749 | 3,073 |
| Apr-29-2024 | 172,822 | -1,231 |
Advertisement
su.pr 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.
su.pr 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.
Domain Name: SU.PR
Registry Domain ID: D425500000017210862-AGRS
Registrar WHOIS Server:
Registrar URL: http://www.markmonitor.com
Updated Date: 2020-01-12T10:07:38Z
Creation Date: 2009-02-13T11:24:55Z
Registry Expiry Date: 2022-02-13T00:00:00Z
Registrar Registration Expiration Date:
Registrar: MarkMonitor Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2083895740
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
Registry Registrant ID: C20896885-AGRS
Registrant Name: Domain Administrator
Registrant Organization: Stumbleupon Inc.
Registrant Street: 301 Brannan St
Registrant City: San Francisco
Registrant State/Province: CA
Registrant Postal Code: 94107
Registrant Country: US
Registrant Phone: +1.4154306301
Registrant Phone Ext:
Registrant Fax: +1.4154306301
Registrant Fax Ext:
Registrant Email: hostmaster@stumbleupon.com
Registry Admin ID: C20896885-AGRS
Admin Name: Domain Administrator
Admin Organization: Stumbleupon Inc.
Admin Street: 301 Brannan St
Admin City: San Francisco
Admin State/Province: CA
Admin Postal Code: 94107
Admin Country: US
Admin Phone: +1.4154306301
Admin Phone Ext:
Admin Fax: +1.4154306301
Admin Fax Ext:
Admin Email: hostmaster@stumbleupon.com
Registry Tech ID: C20896885-AGRS
Tech Name: Domain Administrator
Tech Organization: Stumbleupon Inc.
Tech Street: 301 Brannan St
Tech City: San Francisco
Tech State/Province: CA
Tech Postal Code: 94107
Tech Country: US
Tech Phone: +1.4154306301
Tech Phone Ext:
Tech Fax: +1.4154306301
Tech Fax Ext:
Tech Email: hostmaster@stumbleupon.com
Name Server: NS1.P08.DYNECT.NET
Name Server: NS2.P08.DYNECT.NET
Name Server: NS3.P08.DYNECT.NET
Name Server: NS4.P08.DYNECT.NET
Name Server: DNS1.P08.NSONE.NET
Name Server: DNS2.P08.NSONE.NET
Name Server: DNS3.P08.NSONE.NET
Name Server: DNS4.P08.NSONE.NET
DNSSEC: unsigned
>>> Last update of WHOIS database: 2021-05-25T09:22:40Z
su.pr server information
Servers Location
| IP Address |
|---|
| Country |
|---|
su.pr desktop page speed rank
Last tested: 2017-05-23
su.pr Desktop Speed Test Quick Summary
priority - 14 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 136.4KiB (50% reduction).
Compressing https://nb9-stumbleupon.netdna-ssl.com/lW50qvOVBqxKc-OA5ppbxA could save 2.8KiB (84% reduction).
priority - 12 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script 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:
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://www.stumbleupon.com/
https://www.stumbleupon.com/
priority - 6 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 53.5KiB (31% reduction).
Minifying https://nb9-stumbleupon.netdna-ssl.com/V9IynOEVLYLYQ0MsAEHyWw could save 10.9KiB (27% reduction) after compression.
Minifying https://nb9-stumbleupon.netdna-ssl.com/GpxW7L0b4BZ7lAHIQj4tnQ could save 610B (24% reduction) after compression.
priority - 4 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://cdn.optimizely.com/js/651393494.js (2.1 minutes)
https://s.adroll.com/j/roundtrip.js (5 minutes)
https://s.adroll.com/pixel/IX6UHXJ2HBEUVIX7PDO6BT/…XOSVFSVDWPDJPQLT5OR.js (5 minutes)
https://connect.facebook.net/en_US/all.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/1495186034074188?v=2.7.11 (20 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)
priority - 1 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 12.2KiB (60% reduction).
priority - 1 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 5.6KiB (18% reduction).
Minifying https://nb9-stumbleupon.netdna-ssl.com/uWymphkCVscsqufHW_cV1Q could save 1.9KiB (14% reduction) after compression.
su.pr Desktop Resources
| Total Resources | 68 |
| Number of Hosts | 28 |
| Static Resources | 30 |
| JavaScript Resources | 24 |
| CSS Resources | 5 |
su.pr Desktop Resource Breakdown
su.pr mobile page speed rank
Last tested: 2018-06-03
su.pr Mobile Speed Test Quick Summary
priority - 20 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 195.7KiB (34% reduction).
Minifying https://dv4uxy777adjt.cloudfront.net/assets/widget…b2d55977e7f2b008766.js could save 30.1KiB (45% reduction) after compression.
Minifying https://dwxmyiyf7jg6.cloudfront.net/assets/widget_…8a09771dd71de059c67.js could save 4KiB (75% reduction) after compression.
Minifying http://platform.stumbleupon.com/1/widgets.js could save 1.2KiB (29% reduction) after compression.
Minifying https://platform.stumbleupon.com/1/widgets.js could save 1.2KiB (29% reduction) after compression.
Minifying https://platform.stumbleupon.com/1/widgets.js?_=1528010184891 could save 1.2KiB (29% reduction) after compression.
Minifying https://d37h3y471q0lt2.cloudfront.net/assets/widge…e826846ba09ecea0c4a.js could save 1KiB (61% reduction) after compression.
Minifying https://dwxmyiyf7jg6.cloudfront.net/assets/widget_…bd4f4156f2ff4a717f3.js could save 402B (23% reduction) after compression.
priority - 13 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.stumbleupon.com/api/v2_0/interests (expiration not specified)
https://cdn.optimizely.com/js/651393494.js (2 minutes)
http://a.adroll.com/j/roundtrip.js (5 minutes)
https://s.adroll.com/j/roundtrip.js (5 minutes)
https://s.adroll.com/pixel/IX6UHXJ2HBEUVIX7PDO6BT/…XOSVFSVDWPDJPQLT5OR.js (5 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://connect.facebook.net/signals/config/1495186…4188?v=2.8.14&r=stable (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/en_US/sdk.js (20 minutes)
https://connect.facebook.net/signals/config/149518…4188?v=2.8.14&r=stable (20 minutes)
http://beacon.errorception.com/530bcc7986a669467a000263.js (60 minutes)
https://beacon.errorception.com/530bcc7986a669467a000263.js (60 minutes)
http://platform.stumbleupon.com/1/widgets.js (2 hours)
http://www.google-analytics.com/ga.js (2 hours)
https://platform.stumbleupon.com/1/widgets.js (2 hours)
https://platform.stumbleupon.com/1/widgets.js?_=1528010184891 (2 hours)
https://ssl.google-analytics.com/ga.js (2 hours)
priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 6 blocking script resources and 6 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://loader.engage.gsfn.us/loader.js
https://cdn.optimizely.com/js/651393494.js
https://loader.engage.gsfn.us/loader.js
Use asynchronous versions of the following scripts:
https://platform.stumbleupon.com/1/widgets.js
Optimize CSS Delivery of the following:
http://fonts.googleapis.com/css?family=Oswald%7CLato%7CRaleway&subset=latin
https://dv4uxy777adjt.cloudfront.net/assets/widget…c046ed1d6800cee8d5.css
https://dv4uxy777adjt.cloudfront.net/assets/widget…c046ed1d6800cee8d5.css
https://nb9-stumbleupon.netdna-ssl.com/y_PSSsURr6YpIjzG_5fFNA
https://fonts.googleapis.com/css?family=Oswald%7CL…7CRaleway&subset=latin
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 - 1 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 10.3KiB (67% reduction).
priority - 0 Reduce server response time
In our test, your server responded in 0.22 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
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 2.3KiB (16% reduction).
Minifying https://www.stumbleupon.com/ could save 1.1KiB (16% reduction) after compression.
priority - 0 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 374B (20% reduction).
su.pr Mobile Resources
| Total Resources | 78 |
| Number of Hosts | 30 |
| Static Resources | 32 |
| JavaScript Resources | 33 |
| CSS Resources | 4 |
su.pr Mobile Resource Breakdown
su.pr mobile page usability
Last tested: 2018-06-03
su.pr similar domains
www.su.net
www.su.org
www.su.info
www.su.biz
www.su.us
www.su.mobi
www.u.pr
www.su.pr
www.wu.pr
www.swu.pr
www.wsu.pr
www.eu.pr
www.seu.pr
www.esu.pr
www.du.pr
www.sdu.pr
www.dsu.pr
www.zu.pr
www.szu.pr
www.zsu.pr
www.xu.pr
www.sxu.pr
www.xsu.pr
www.au.pr
www.sau.pr
www.asu.pr
www.s.pr
www.sy.pr
www.suy.pr
www.syu.pr
www.sh.pr
www.suh.pr
www.shu.pr
www.sj.pr
www.suj.pr
www.sju.pr
www.si.pr
www.sui.pr
www.siu.pr
su.pr 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.
su.pr 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.