foller.me website information.
foller.me domain name is registered by .ME top-level domain registry. See the other sites registred in .ME domain zone.
Following name servers are specified for foller.me domain:
- barbara.ns.cloudflare.com
- marty.ns.cloudflare.com
and probably website foller.me is hosted by FASTLY - Fastly, US web hosting company. Check the complete list of other most popular websites hosted by FASTLY - Fastly, US hosting company.
According to Alexa traffic rank the highest website foller.me position was 20384 (in the world). The lowest Alexa rank position was 997290. Now website foller.me ranked in Alexa database as number 313708 (in the world).
Website foller.me Desktop speed measurement score (88/100) is better than the results of 85.98% of other sites and shows that the page is performing great on desktop computers.
foller.me Mobile usability score (65/100) is better than the results of 13.11% of other sites and shows that the page mobile usability is poor and can be improved.
Mobile speed measurement score of foller.me (73/100) is better than the results of 81.47% 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 |
---|---|---|
Sep-23-2024 | 313,708 | 4,588 |
Sep-22-2024 | 318,296 | 896 |
Sep-21-2024 | 319,192 | 10,707 |
Sep-20-2024 | 329,899 | -10,272 |
Sep-19-2024 | 319,627 | 7,407 |
Sep-18-2024 | 327,034 | -2,730 |
Sep-17-2024 | 324,304 | 8,400 |
Advertisement
foller.me 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.
foller.me 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: FOLLER.ME
Registry Domain ID: D108500000000707821-AGRS
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: www.namecheap.com
Updated Date: 2021-05-17T07:12:30Z
Creation Date: 2009-05-23T13:51:53Z
Registry Expiry Date: 2022-05-23T13:51:53Z
Registrar Registration Expiration Date:
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Reseller:
Domain Status: ok https://icann.org/epp#ok
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant State/Province: Capital Region
Registrant Country: IS
Name Server: NS1.PRESSJITSU.COM
Name Server: NS2.PRESSJITSU.COM
Name Server: NS3.PRESSJITSU.COM
Name Server: NS4.PRESSJITSU.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2021-06-02T21:42:55Z
foller.me server information
foller.me desktop page speed rank
Last tested: 2017-06-06
foller.me Desktop Speed Test Quick Summary
priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 3 blocking script resources and 2 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://foller.me/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
https://foller.me/wp-content/themes/follerme/bootstrap-twipsy.js
Optimize CSS Delivery of the following:
https://foller.me/wp-content/themes/follerme/bootstrap.min.css
priority - 2 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://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)
priority - 2 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 14.8KiB (44% reduction).
Compressing https://pbs.twimg.com/profile_images/718514084669337600/y3kdhY57_normal.jpg could save 1,004B (51% reduction).
Compressing https://pbs.twimg.com/profile_images/704150135756840960/-rTfOGbw_normal.jpg could save 966B (61% reduction).
Compressing https://pbs.twimg.com/profile_images/866928288140333056/CVrzhLH-_normal.jpg could save 965B (48% reduction).
Compressing https://pbs.twimg.com/profile_images/772908880380698624/xoY1StY-_normal.jpg could save 960B (50% reduction).
Compressing https://pbs.twimg.com/profile_images/843197710735982594/WJAcxFRs_normal.jpg could save 945B (47% reduction).
Compressing https://pbs.twimg.com/profile_images/870746889699962880/IAwEJ6Jf_normal.jpg could save 938B (42% reduction).
Compressing https://pbs.twimg.com/profile_images/828172523057602560/xb_ChB-C_normal.jpg could save 923B (58% reduction).
Compressing https://pbs.twimg.com/profile_images/859199346683891712/uRDMaVib_normal.jpg could save 917B (41% reduction).
Compressing https://pbs.twimg.com/profile_images/854357553144143872/UWIvM8f-_normal.jpg could save 912B (49% reduction).
Compressing https://pbs.twimg.com/profile_images/740125552758132736/YGTrSlhJ_normal.jpg could save 910B (47% reduction).
Compressing https://pbs.twimg.com/profile_images/762741517752623104/qSITHVsS_normal.jpg could save 906B (43% reduction).
Compressing https://pbs.twimg.com/profile_images/5430773392155…6/Ba0yyrjC_normal.jpeg could save 759B (41% reduction).
Compressing https://pbs.twimg.com/profile_images/651516563946803200/Boo9voM-_normal.jpg could save 748B (46% reduction).
Compressing https://pbs.twimg.com/profile_images/4459617822809…9/yjD_jrr2_normal.jpeg could save 738B (35% reduction).
Compressing https://pbs.twimg.com/profile_images/671615921082015744/GEK5ZkVF_normal.jpg could save 704B (36% reduction).
Compressing https://pbs.twimg.com/profile_images/652675456135643136/L4Ey8nAf_normal.jpg could save 689B (40% reduction).
priority - 0 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 867B (35% reduction).
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 617B (12% reduction).
foller.me Desktop Resources
Total Resources | 51 |
Number of Hosts | 13 |
Static Resources | 39 |
JavaScript Resources | 17 |
CSS Resources | 2 |
foller.me Desktop Resource Breakdown
foller.me mobile page speed rank
Last tested: 2017-05-24
foller.me Mobile Speed Test Quick Summary
priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 3 blocking script resources and 2 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://foller.me/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
https://foller.me/wp-content/themes/follerme/bootstrap-twipsy.js
Optimize CSS Delivery of the following:
https://foller.me/wp-content/themes/follerme/bootstrap.min.css
priority - 3 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://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)
priority - 2 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 19.4KiB (50% reduction).
Compressing https://pbs.twimg.com/profile_images/864174326731476995/m04x7mXL_normal.jpg could save 960B (44% reduction).
Compressing https://pbs.twimg.com/profile_images/822745962598629380/AAZnnFGb_normal.jpg could save 957B (40% reduction).
Compressing https://pbs.twimg.com/profile_images/856644512780865536/X0ABBomV_normal.jpg could save 951B (49% reduction).
Compressing https://pbs.twimg.com/profile_images/866665453778870272/oqalWYLz_normal.jpg could save 948B (50% reduction).
Compressing https://pbs.twimg.com/profile_images/858730323236016128/y_clZ_q5_normal.jpg could save 936B (46% reduction).
Compressing https://pbs.twimg.com/profile_images/863918507343400964/tQu20oCJ_normal.jpg could save 923B (53% reduction).
Compressing https://pbs.twimg.com/profile_images/851161685431865344/ImsXu2eU_normal.jpg could save 919B (44% reduction).
Compressing https://pbs.twimg.com/profile_images/831705633279795200/qFdmOaqv_normal.jpg could save 903B (42% reduction).
Compressing https://pbs.twimg.com/profile_images/867199249989160960/bQHQC7St_normal.jpg could save 901B (43% reduction).
Compressing https://pbs.twimg.com/profile_images/864614942502043648/kJQrn43a_normal.jpg could save 898B (43% reduction).
Compressing https://pbs.twimg.com/profile_images/857748495243018240/IWpcyYJa_normal.jpg could save 875B (41% reduction).
Compressing https://pbs.twimg.com/profile_images/5415775306211…6/zlKBIOet_normal.jpeg could save 734B (47% reduction).
Compressing https://pbs.twimg.com/profile_images/1931954379/image_normal.jpg could save 731B (36% reduction).
Compressing https://pbs.twimg.com/profile_images/636738947566071809/2N6IoZHH_normal.jpg could save 727B (44% reduction).
Compressing https://pbs.twimg.com/profile_images/580758074748579841/GcO0-48A_normal.jpg could save 720B (40% reduction).
Compressing https://pbs.twimg.com/profile_images/677841323760689153/0M115b01_normal.jpg could save 706B (38% reduction).
priority - 0 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 867B (35% reduction).
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 614B (12% reduction).
foller.me Mobile Resources
Total Resources | 47 |
Number of Hosts | 11 |
Static Resources | 37 |
JavaScript Resources | 15 |
CSS Resources | 2 |
foller.me Mobile Resource Breakdown
foller.me mobile page usability
Last tested: 2017-05-24
foller.me Mobile Usability Test Quick Summary
priority - 30 Use 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.
foller.me
renders only 8 pixels tall (20 CSS pixels).beta
renders only 8 pixels tall (20 CSS pixels).Home
renders only 5 pixels tall (13 CSS pixels).Foller.me
renders only 7 pixels tall (18 CSS pixels).is a Twitter a…tion and more!
renders only 7 pixels tall (18 CSS pixels).Here's how it works
and 1 others render only 7 pixels tall (18 CSS pixels).We take you th…ated accounts.
and 11 others render only 5 pixels tall (13 CSS pixels).followers ratio
and 2 others render only 5 pixels tall (13 CSS pixels).@
renders only 5 pixels tall (13 CSS pixels).Analyze
renders only 5 pixels tall (13 CSS pixels).Note:
renders only 5 pixels tall (13 CSS pixels).The above acco…experience ;)
and 1 others render only 5 pixels tall (13 CSS pixels).Live examples
and 6 others render only 6 pixels tall (16 CSS pixels).NOTE
renders only 4 pixels tall (10 CSS pixels).How we analyze those tweets
renders only 7 pixels tall (18 CSS pixels).NEW!
and 2 others render only 4 pixels tall (10 CSS pixels).using the Twit…Twitter, Inc.
and 2 others render only 5 pixels tall (13 CSS pixels).Konstantin Kovshenin
and 1 others render only 5 pixels tall (13 CSS pixels).Tweet
renders only 5 pixels tall (13 CSS pixels).Like
renders only 4 pixels tall (11 CSS pixels).58
renders only 4 pixels tall (11 CSS pixels).67
renders only 4 pixels tall (10 CSS pixels).priority - 15 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.
<a href="https://foller.me/mynamachef"></a>
and 17 others are close to other tap targets.<form id="u_0_1">Like58</form>
is close to 1 other tap targets.<button id="u_0_2" type="submit" class="inlineBlock _2tga _49ve">Like58</button>
is close to 1 other tap targets.priority - 10 Configure 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.
Configure a viewport for this page.
foller.me similar domains
www.foller.net
www.foller.org
www.foller.info
www.foller.biz
www.foller.us
www.foller.mobi
www.oller.me
www.foller.me
www.coller.me
www.fcoller.me
www.cfoller.me
www.doller.me
www.fdoller.me
www.dfoller.me
www.roller.me
www.froller.me
www.rfoller.me
www.toller.me
www.ftoller.me
www.tfoller.me
www.goller.me
www.fgoller.me
www.gfoller.me
www.voller.me
www.fvoller.me
www.vfoller.me
www.fller.me
www.filler.me
www.foiller.me
www.fioller.me
www.fkller.me
www.fokller.me
www.fkoller.me
www.flller.me
www.folller.me
www.floller.me
www.fpller.me
www.fopller.me
www.fpoller.me
www.foler.me
www.fopler.me
www.folpler.me
www.fooler.me
www.fololer.me
www.fooller.me
www.fokler.me
www.folkler.me
www.folper.me
www.follper.me
www.foloer.me
www.folloer.me
www.folker.me
www.follker.me
www.follr.me
www.follwr.me
www.follewr.me
www.follwer.me
www.follsr.me
www.follesr.me
www.follser.me
www.folldr.me
www.folledr.me
www.follder.me
www.follrr.me
www.follerr.me
www.follrer.me
www.folle.me
www.follee.me
www.follere.me
www.folleer.me
www.folled.me
www.follerd.me
www.follef.me
www.follerf.me
www.follefr.me
www.follet.me
www.follert.me
www.folletr.me
foller.me 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.
foller.me 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.