Phono is ranked 17,175,403 in the United Kingdom. 'Phono - jQuery Phone Plugin.'
17,175,403Rank in United Kingdom
625,074Worldwide Rank
Monthly pages viewed | 67,813 | |
Monthly visits | 26,082 | |
Value per visitor | -- | |
Estimated worth | £9,157.42 | |
External links | 439 | |
Number of pages | 360 |
Last Updated: 06/04/2018 . Estimated data, read disclaimer.
Visitors
Country | Country Rank | Users % | Pageviews % |
Other countries | 84.50% | 83.10% | |
---|---|---|---|
United States | 486,435 | 15.70% | 16.90% |
The majority of visitors come from United States.
Traffic History 90 Day Average | ||
Worldwide Rank | 525,272 | -900 |
---|---|---|
Daily Visitors | 599 | -1.74% |
Daily Visitors Rank | 507,293 | -23,876 |
Daily Pageviews | 1,050 | -17.01% |
Daily Pageviews Rank | 676,806 | 54,114 |
Pageviews Per User | 2.60 | -15.28% |
www.Phono.com
Topics: Learn How, Download, Documentation, Demos, Forums, and Webrtc.
Age: It went live on September 28th 1999, making it over 18 years, 6 months old.
- Popular pages
- phono.com Phono Mobile | Real-Time Audio and Messaging for iOS and Android ..
- blog.phono.com The Phono Blog
- blog.phono.com The Phono Blog » Video: How To Build an iPhone Voice ..
- blog.phono.com The Phono Blog » Building a Remote Call Center with JavaScript
On average 2.60 pages are viewed each, by the estimated 655 daily visitors.
Links- Links out
- w3.org World Wide Web Consortium (W3C)
- jquery.com jQuery: The Write Less, Do More, JavaScript Library
- asterisk.org Asterisk- The Open Source Telephony Projects | Asterisk
- voxeo.com IVR Platforms / IVR Hosting / IVR Development
Server Location | |
Amazon.com Inc. Washington Seattle United States 47.501, -122.358 |
It is hosted by Amazon.com Inc (Washington, Seattle,) using nginx/1 web server. dns4.voxeo.net, dns2.voxeo.net, and dns1.voxeo.net are some of its 4 Nameservers. Phono.com's IP address is 184.73.171.204.
IP: 184.73.171.204
Web Server: nginx/1
Encoding: utf-8
PING proxy.heroku.com (184.73.173.41) 56(84) bytes of data. | |
64 bytes from ec2-184-73-173-41.compute-1.amazonaws.com (184.73.173.41): icmp_req=1 ttl=49 | 35.3 ms |
64 bytes from ec2-184-73-173-41.compute-1.amazonaws.com (184.73.173.41): icmp_req=2 ttl=49 | 35.3 ms |
64 bytes from ec2-184-73-173-41.compute-1.amazonaws.com (184.73.173.41): icmp_req=3 ttl=49 | 35.2 ms |
--- proxy.heroku.com ping statistics --- | |
3 packets transmitted, 3 received, 0% packet loss, time 2003ms | |
rtt min/avg/max/mdev = 35.295/35.306/35.321/0.217 ms | |
rtt min/avg/max/mdev = 35.295/35.306/35.321/0.217 ms |
A time of 35.3 ms is recorded in a ping test, also its average full page load time is 1609 milliseconds. This is slower than 42% of measured websites.
Server Setup | |
Server: | nginx/1.0.5 |
---|---|
Date: | -- |
Content-Type: | text/html; charset=utf-8 |
Transfer-Encoding: | chunked |
Connection: | keep-alive |
Status: | 200 OK |
X-UA-Compatible: | IE=Edge,chrome=1 |
ETag: | "aad59ff055ec2e0e66150a225dc14cda" |
Cache-Control: | max-age=0, private, must-revalidate |
X-Runtime: | 0.004095 |
X-Rack-Cache: | miss |