img.ly Website Information
Daily Unique Visits: 16,087
Daily Page Views: 96,522
Income Per Day: $193
Estimated Value: $138,960
This website is located in United States and is using following IP address 13.35.125.34. See the complete list of popular websites hosted in United States.
img.ly is registered under .LY top-level domain. Please check other sites in .LY zone.
Website img.ly is using the following name servers:
- ns1.dnsimple.com
- ns2.dnsimple.com
- ns3.dnsimple.com
- ns4.dnsimple.com
and is probably hosted by GOOGLE - Google LLC, US. See the full list of other websites hosted by GOOGLE - Google LLC, US.
The highest website img.ly position in Alexa rank database was 18608 and the lowest rank position was 996739. Current position of img.ly in Alexa rank database is 89153.
Desktop speed score of img.ly (89/100) is better than the results of 87.7% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of img.ly (65/100) is better than the results of 13.11% of other sites and means that the page is not mobile-friendly.
Mobile speed score of img.ly (72/100) is better than the results of 79.79% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
img.ly 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.
img.ly 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.
Registry Domain ID: 31828-CoCCA
Registry WHOIS Server: whois.nic.ly
Updated Date: 2022-03-28T20:24:35.651Z
Creation Date: 2009-03-23T22:00:00.0Z
Registry Expiry Date: 2025-03-23T22:00:00.0Z
Registrar Registration Expiration Date: 2025-03-23T22:00:00.0Z
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: ZFmfV-EvjTB
Registrant Name: Eray Basar
Registrant Organization: Basar Deutsch GBR
Registrant Street: Kortumstrasse 19-21
Registrant City: Bochum
Registrant State/Province: NRW
Registrant Postal Code: 44787
Registrant Country: LY
Registrant Phone: +234.6894188
Registrant Email: eray.basar@9elements.com
Registrar: Libyan Spider Network (loc)
Registrar Abuse Contact Email: abuse@libyanspider.com
Registrar Abuse Contact Phone: +218.213632323
Name Server: ns1.dnsimple.com
Name Server: ns2.dnsimple.com
Name Server: ns3.dnsimple.com
Name Server: ns4.dnsimple.com
DNSSEC: unsigned
>>> Last update of WHOIS database: 2024-09-18T02:53:59.680Z
img.ly server information
Servers Location
img.ly desktop page speed rank
Last tested: 2017-05-10
img.ly 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:
priority - 2Leverage 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://connect.facebook.net/en_US/all.js (20 minutes)
http://s3.buysellads.com/ac/bsa.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
https://js-agent.newrelic.com/nr-1026.min.js (2 hours)
img.ly Desktop Resource Breakdown
| Total Resources | 20 |
| Number of Hosts | 11 |
| Static Resources | 11 |
| JavaScript Resources | 8 |
| CSS Resources | 1 |
img.ly mobile page speed rank
Last tested: 2017-04-28
img.ly 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:
priority - 4Leverage 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.googletagservices.com/tag/js/gpt.js (15 minutes)
http://connect.facebook.net/en_US/all.js (20 minutes)
http://s3.buysellads.com/ac/bsa.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
https://js-agent.newrelic.com/nr-1026.min.js (2 hours)
priority - 2Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 17.7KiB (66% reduction).
img.ly Mobile Resource Breakdown
| Total Resources | 20 |
| Number of Hosts | 11 |
| Static Resources | 11 |
| JavaScript Resources | 8 |
| CSS Resources | 1 |
img.ly mobile page usability
Last tested: 2017-04-28
img.ly Mobile Usability Test Quick Summary
priority - 40Use 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.
Something awes…in the making. renders only 7 pixels tall (18 CSS pixels).on 31st July.…ter this date. and 4 others render only 7 pixels tall (18 CSS pixels).twitter photo sharing service renders only 7 pixels tall (18 CSS pixels).Photo Editor SDK renders only 7 pixels tall (18 CSS pixels).(c) 2016 9elements Gmbh and 1 others render only 4 pixels tall (10 CSS pixels).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 - 5Size 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.
<input type="email" name="EMAIL" class="email-input"> is close to 1 other tap targets.<input type="submit" class="email-input"> is close to 1 other tap targets.img.ly HTML validation
Warnings
Consider avoiding viewport values that prevent users from resizing documents.
"...script> <meta content='width=device-width, initial-scale=1.0, maximum-scale=1.0' name='viewport'> </hea..."
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
"...section> <section class="home-footer"> <p>..."
img.ly similar domains
www.img.net
www.img.org
www.img.info
www.img.biz
www.img.us
www.img.mobi
www.mg.ly
www.img.ly
www.umg.ly
www.iumg.ly
www.uimg.ly
www.jmg.ly
www.ijmg.ly
www.jimg.ly
www.kmg.ly
www.ikmg.ly
www.kimg.ly
www.omg.ly
www.iomg.ly
www.oimg.ly
www.ig.ly
www.ing.ly
www.imng.ly
www.inmg.ly
www.ijg.ly
www.imjg.ly
www.ikg.ly
www.imkg.ly
www.im.ly
www.imf.ly
www.imgf.ly
www.imfg.ly
www.imv.ly
www.imgv.ly
www.imvg.ly
www.imt.ly
www.imgt.ly
www.imtg.ly
www.imb.ly
www.imgb.ly
www.imbg.ly
www.imy.ly
www.imgy.ly
www.imyg.ly
www.imh.ly
www.imgh.ly
www.imhg.ly
img.ly 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.
img.ly 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.