href.li Website Information
Daily Unique Visits: 255,725
Daily Page Views: 2,045,800
Income Per Day: $2,046
Estimated Value: $2,209,680
href.li is registered under .LI top-level domain. Please check other sites in .LI zone.
No name server records were found.
and is probably hosted by AUTOMATTIC - Automattic, Inc, US. See the full list of other websites hosted by AUTOMATTIC - Automattic, Inc, US.
The highest website href.li position in Alexa rank database was 2441 and the lowest rank position was 6189. Current position of href.li in Alexa rank database is 5959.
Desktop speed score of href.li (91/100) is better than the results of 90.07% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of href.li (75/100) is better than the results of 23.63% of other sites and means that the page is not mobile-friendly.
Mobile speed score of href.li (75/100) is better than the results of 84.42% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
href.li Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
href.li whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
href.li server information
Servers Location
href.li desktop page speed rank
Last tested: 2017-04-27
href.li Desktop Speed Test Quick Summary
priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
href.li Desktop Resource Breakdown
Total Resources | 4 |
Number of Hosts | 1 |
Static Resources | 2 |
JavaScript Resources | 1 |
CSS Resources | 1 |
href.li mobile page speed rank
Last tested: 2017-04-27
href.li Mobile Speed Test Quick Summary
priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
href.li Mobile Resource Breakdown
Total Resources | 4 |
Number of Hosts | 1 |
Static Resources | 2 |
JavaScript Resources | 1 |
CSS Resources | 1 |
href.li mobile page usability
Last tested: 2017-04-27
href.li Mobile Usability Test Quick Summary
priority - 17Size 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.
<label for="url">Hide the referrer to your URL:</label>
is close to 1 other tap targets.<input id="url" type="text" name="url" class="fselect">
is close to 1 other tap targets.<input type="submit" name="make">
is close to 2 other tap targets.priority - 10Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
priority - 5Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
Create an anon…link that will
and 1 others render only 6 pixels tall (16 CSS pixels).hide the HTTP Referer
renders only 6 pixels tall (16 CSS pixels).href.li
renders only 5 pixels tall (13 CSS pixels).bookmarklet -…owser toolbar.
renders only 5 pixels tall (13 CSS pixels).href.li HTML validation
Errors
Almost standards mode doctype. Expected “<!DOCTYPE html>”.
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."
End tag for “body” seen, but there were unclosed elements.
"...bar.</p> </body> </htm..."
Unclosed element “div”.
"...> <body> <div id="wrap"> <h1>..."
href.li similar domains
www.href.net
www.href.org
www.href.info
www.href.biz
www.href.us
www.href.mobi
www.ref.li
www.href.li
www.bref.li
www.hbref.li
www.bhref.li
www.gref.li
www.hgref.li
www.ghref.li
www.yref.li
www.hyref.li
www.yhref.li
www.uref.li
www.huref.li
www.uhref.li
www.jref.li
www.hjref.li
www.jhref.li
www.nref.li
www.hnref.li
www.nhref.li
www.hef.li
www.heef.li
www.hreef.li
www.heref.li
www.hdef.li
www.hrdef.li
www.hdref.li
www.hfef.li
www.hrfef.li
www.hfref.li
www.htef.li
www.hrtef.li
www.htref.li
www.hrf.li
www.hrwf.li
www.hrewf.li
www.hrwef.li
www.hrsf.li
www.hresf.li
www.hrsef.li
www.hrdf.li
www.hredf.li
www.hrrf.li
www.hrerf.li
www.hrref.li
www.hre.li
www.hrec.li
www.hrefc.li
www.hrecf.li
www.hred.li
www.hrefd.li
www.hrer.li
www.hrefr.li
www.hret.li
www.hreft.li
www.hretf.li
www.hreg.li
www.hrefg.li
www.hregf.li
www.hrev.li
www.hrefv.li
www.hrevf.li
href.li Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
href.li TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.