followup.cc Website Information

Daily Unique Visits: 19,930

Daily Page Views: 119,580

Income Per Day: $239

Estimated Value: $172,080

This website is located in United States and is using following IP address 34.216.166.12. See the complete list of popular websites hosted in United States.

followup.cc is registered under .CC top-level domain. Please check other sites in .CC zone.

Website followup.cc is using the following name servers:

ns-1497.awsdns-59.org
ns-1877.awsdns-42.co.uk
ns-23.awsdns-02.com
ns-676.awsdns-20.net

and is probably hosted by AMAZON-02 - Amazon.com, Inc., US. See the full list of other websites hosted by AMAZON-02 - Amazon.com, Inc., US.

The highest website followup.cc position in Alexa rank database was 16699 and the lowest rank position was 969966. Current position of followup.cc in Alexa rank database is 71965.

Desktop speed score of followup.cc (68/100) is better than the results of 47.59% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of followup.cc (86/100) is better than the results of 27.73% of other sites and means that the page is mobile-friendly.

Mobile speed score of followup.cc (50/100) is better than the results of 33.92% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

followup.cc 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.

followup.cc 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.

Domain Name: FOLLOWUP.CC
Registry Domain ID: 87474999_DOMAIN_CC-VRSN
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2024-08-24T15:08:52Z
Creation Date: 2007-08-27T22:26:04Z
Registry Expiry Date: 2026-08-27T22:26:04Z
Registrar: Gandi SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: abuse@support.gandi.net
Registrar Abuse Contact Phone: +33.170377661
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS-1497.AWSDNS-59.ORG
Name Server: NS-1877.AWSDNS-42.CO.UK
Name Server: NS-23.AWSDNS-02.COM
Name Server: NS-676.AWSDNS-20.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-09-16T23:25:00Z

followup.cc server information

Servers Location

followup.cc desktop page speed rank

Last tested: 2016-10-10

Desktop Speed Medium

68/100

followup.cc Desktop Speed Test Quick Summary

priority - 22Enable 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 211.7KiB (74% reduction).

Compressing https://cdn.followup.cc/assets/website/website-956…4684a535f8e29acc76.css could save 119.9KiB (81% reduction).
Compressing https://cdn.followup.cc/assets/website/website-848…74d46ff53df21a05f24.js could save 87.4KiB (67% reduction).
Compressing https://s3.amazonaws.com/V3-Assets/prod/client_super_tag/json3.js could save 4.4KiB (57% reduction).

priority - 14Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://cdn.followup.cc/assets/website/website-848…74d46ff53df21a05f24.js
https://cdn.optimizely.com/js/3317940102.js
https://cdn.followup.cc/assets/website/website_hom…a2ea2ba5a0caf8c292c.js
https://cdn.followup.cc/assets/website/website_sti…87f3e29936aef7a749c.js

Optimize CSS Delivery of the following:

https://cdn.followup.cc/assets/website/website-956…4684a535f8e29acc76.css
https://fonts.googleapis.com/css?family=Lobster|Lato:300,400,700,900

priority - 7Leverage 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://api.segment.io/v1/p (expiration not specified)
https://api.segment.io/v1/t (expiration not specified)
https://nexus-websocket-a.intercom.io/client-test (expiration not specified)
https://nexus-websocket-b.intercom.io/client-test (expiration not specified)
https://s3.amazonaws.com/V3-Assets/prod/client_super_tag/init_super_tag.js (expiration not specified)
https://static.hotjar.com/c/hotjar-168947.js?sv=5 (60 seconds)
https://cdn.segment.com/analytics.js/v1/RaK5KhFBIy…DwkfV/analytics.min.js (2 minutes)
https://cdn.optimizely.com/js/3317940102.js (2.1 minutes)
https://cdn.mxpnl.com/libs/mixpanel-2-latest.min.js (5 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-PMZ3SR (15 minutes)
https://apis.google.com/js/plusone.js?onload=onLoadCallback (30 minutes)
https://js-agent.newrelic.com/nr-974.min.js (60 minutes)
https://s3.amazonaws.com/V3-Assets/prod/client_super_tag/json3.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 5Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 48.1KiB (46% reduction).

Compressing and resizing https://cdn.followup.cc/assets/website/home/websit…da02bc0c1c803cd0a5.png could save 19.5KiB (62% reduction).
Compressing and resizing https://cdn.followup.cc/assets/website/home/websit…66f6821f92aa2828e9.png could save 12.2KiB (50% reduction).
Compressing and resizing https://cdn.followup.cc/assets/website/home/websit…9b2444c3faee99aabf.png could save 4.8KiB (45% reduction).
Compressing and resizing https://cdn.followup.cc/assets/website/home/websit…422bfbce5503f03768.png could save 4.5KiB (44% reduction).
Compressing and resizing https://cdn.followup.cc/assets/website/home/websit…41d7f47ea1929223ca.png could save 4.4KiB (50% reduction).
Compressing https://cdn.followup.cc/assets/website/home/websit…1a922dc19a824bd16f.jpg could save 1KiB (12% reduction).
Compressing https://cdn.followup.cc/assets/website/home/websit…a4dddff4450fab0221.jpg could save 1,003B (11% reduction).
Compressing https://cdn.followup.cc/assets/website/home/websit…a0baf9d35b6981b9fd.jpg could save 848B (26% reduction).

followup.cc Desktop Resource Breakdown

Total Resources	79
Number of Hosts	31
Static Resources	49
JavaScript Resources	32
CSS Resources	2

followup.cc mobile page speed rank

Last tested: 2019-12-15

Mobile Speed Bad

50/100

followup.cc Mobile Speed Test Quick Summary

priority - 48Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://cdn.optimizely.com/js/3317940102.js

Optimize CSS Delivery of the following:

https://followup.cc/website_new/combined.css
https://fonts.googleapis.com/css?family=Karla|Scope+One

priority - 30Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 293.9KiB (63% reduction).

Compressing and resizing https://followup.cc/website_new/remember-everything@2x.png could save 239.1KiB (94% reduction).
Compressing https://followup.cc/website_new/send-later@2x.png could save 28.3KiB (32% reduction).
Compressing https://followup.cc/website_new/email-top-hero@2x.png could save 17.4KiB (24% reduction).
Compressing https://followup.cc/website_new/opened-notification@2x.png could save 4.4KiB (22% reduction).
Compressing https://followup.cc/website_new/proposal-image@2x.png could save 4KiB (17% reduction).
Compressing https://followup.cc/website_new/brand-dark/hbr.png could save 678B (20% reduction).

priority - 20Enable 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 196.3KiB (88% reduction).

Compressing https://followup.cc/website_new/combined.css could save 196.3KiB (88% reduction).

priority - 6Leverage 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/3317940102.js (2 minutes)
https://js.intercomcdn.com/shim.latest.js (5 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-PMZ3SR (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/121708…4751?v=2.9.15&r=stable (20 minutes)
https://connect.facebook.net/signals/config/887759…2189?v=2.9.15&r=stable (20 minutes)
https://static.tapfiliate.com/tapfiliate.js (60 minutes)
https://js-agent.newrelic.com/nr-1153.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 3Minify 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 33.2KiB (16% reduction).

Minifying https://followup.cc/website_new/combined.css could save 33.2KiB (16% reduction).

followup.cc Mobile Resource Breakdown

Total Resources	43
Number of Hosts	20
Static Resources	12
JavaScript Resources	15
CSS Resources	2

followup.cc mobile page usability

Last tested: 2019-12-15

Mobile Usability Good

86/100

followup.cc Mobile Usability Test Quick Summary

priority - 14Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 606 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <img id="email-top-hero" src="/website_new/e…op-hero@2x.png"> falls outside the viewport.
The element <img id="send-later-image" src="/website_new/send-later@2x.png" class="image-shadow"> falls outside the viewport.

followup.cc HTML validation

Errors

Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 6
"...<html> <hea..."

Bad value “https://fonts.googleapis.com/css?family=Karla|Scope+One” for attribute “href” on element “link”: Illegal character in query: “|” is not allowed.

Line: 10 Column: 5 - 90
"...css"> <link href="https://fonts.googleapis.com/css?family=Karla|Scope+One" rel="stylesheet"> ..."

Duplicate ID “nav-pricing”.

Line: 57 Column: 17 - 97
"... <a id="nav-pricing" class="navbar-item" href="https://followup.cc/users/sign_in">Login<..."

Duplicate ID “install-button”.

Line: 76 Column: 20 - 90
"... <p><button class="button is-secondary install-button" id="install-button">Try Fo..." Line: 150 Column: 12 - 80
"... <p><button class="button is-primary install-button" id="install-button">Try Fo..." Line: 191 Column: 20 - 88
"... <p><button class="button is-primary install-button" id="install-button">Try Fo..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 79 Column: 17 - 95
"... <img id="email-top-hero" src="/website_new/email-top-hero@2x.png" data-rjs="2"> ..." Line: 182 Column: 21 - 118
"... <img src="/website_new/send-later@2x.png" id="send-later-image" class="image-shadow" data-rjs="2"> ..."

Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)

Line: 94 Column: - 26
"... <?xml version="1..."

Duplicate ID “Layer_1”.

Line: 126 Column: 21 - 116
"... <svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 40 49.23"><defs>..." Line: 137 Column: 21 - 113
"... <svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 40 40"><defs>..." Line: 401 Column: 82 - 180
"...-twitter"><svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 39.38 39.38"><title..." Line: 404 Column: 90 - 188
"...facebook"><svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 39.38 39.38"><title..." Line: 407 Column: 94 - 192
"...linkedin"><svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 39.38 39.38"><title..."

Duplicate ID “Shape”.

Line: 404 Column: 217 - 230
"...go</title><g id="Shape"><circl..." Line: 407 Column: 221 - 234
"...go</title><g id="Shape"><circl..."

Warnings

The first occurrence of ID “nav-pricing” was here.

Line: 55 Column: 17 - 80
"... <a id="nav-pricing" class="navbar-item" href="#pricing-section">Pricin..."

The first occurrence of ID “install-button” was here.

Line: 59 Column: 21 - 89
"... <button class="button is-primary install-button" id="install-button">Add To..." Line: 59 Column: 21 - 89
"... <button class="button is-primary install-button" id="install-button">Add To..." Line: 59 Column: 21 - 89
"... <button class="button is-primary install-button" id="install-button">Add To..."

The first occurrence of ID “Layer_1” was here.

Line: 97 Column: 1 - 88
"...d 0) --> <svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 64.9 48" style="enable-background:new 0 0 64.9 48;" xml:space="preserve"> <styl..." Line: 97 Column: 1 - 88
"...d 0) --> <svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 64.9 48" style="enable-background:new 0 0 64.9 48;" xml:space="preserve"> <styl..." Line: 97 Column: 1 - 88
"...d 0) --> <svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 64.9 48" style="enable-background:new 0 0 64.9 48;" xml:space="preserve"> <styl..." Line: 97 Column: 1 - 88
"...d 0) --> <svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 64.9 48" style="enable-background:new 0 0 64.9 48;" xml:space="preserve"> <styl..." Line: 97 Column: 1 - 88
"...d 0) --> <svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 64.9 48" style="enable-background:new 0 0 64.9 48;" xml:space="preserve"> <styl..."

The “name” attribute is obsolete. Consider putting an “id” attribute on the nearest container instead.

Line: 211 Column: 1 - 26
"...section> <a name="pricing-section"></a> <..."

The first occurrence of ID “Shape” was here.

Line: 401 Column: 208 - 221
"...go</title><g id="Shape"><circl..." Line: 401 Column: 208 - 221
"...go</title><g id="Shape"><circl..."

This document appears to be written in English. Consider adding “lang="en"” (or variant) to the “html” start tag.

Line: 1 Column: 1 - 6
"...<html> <hea..."

followup.cc similar domains

Similar domains:

www.followup.com
www.followup.net
www.followup.org
www.followup.info
www.followup.biz
www.followup.us
www.followup.mobi
www.ollowup.cc
www.followup.cc
www.collowup.cc
www.fcollowup.cc
www.cfollowup.cc
www.dollowup.cc
www.fdollowup.cc
www.dfollowup.cc
www.rollowup.cc
www.frollowup.cc
www.rfollowup.cc
www.tollowup.cc
www.ftollowup.cc
www.tfollowup.cc
www.gollowup.cc
www.fgollowup.cc
www.gfollowup.cc
www.vollowup.cc
www.fvollowup.cc
www.vfollowup.cc
www.fllowup.cc
www.fillowup.cc
www.foillowup.cc
www.fiollowup.cc
www.fkllowup.cc
www.fokllowup.cc
www.fkollowup.cc
www.flllowup.cc
www.folllowup.cc
www.flollowup.cc
www.fpllowup.cc
www.fopllowup.cc
www.fpollowup.cc
www.folowup.cc
www.foplowup.cc
www.folplowup.cc
www.foolowup.cc
www.fololowup.cc
www.foollowup.cc
www.foklowup.cc
www.folklowup.cc
www.folpowup.cc
www.follpowup.cc
www.foloowup.cc
www.folloowup.cc
www.folkowup.cc
www.follkowup.cc
www.follwup.cc
www.folliwup.cc
www.folloiwup.cc
www.folliowup.cc
www.follkwup.cc
www.follokwup.cc
www.folllwup.cc
www.follolwup.cc
www.follpwup.cc
www.follopwup.cc
www.folloup.cc
www.folloqup.cc
www.followqup.cc
www.folloqwup.cc
www.folloaup.cc
www.followaup.cc
www.folloawup.cc
www.follosup.cc
www.followsup.cc
www.folloswup.cc
www.folloeup.cc
www.followeup.cc
www.folloewup.cc
www.followp.cc
www.followyp.cc
www.followuyp.cc
www.followyup.cc
www.followhp.cc
www.followuhp.cc
www.followhup.cc
www.followjp.cc
www.followujp.cc
www.followjup.cc
www.followip.cc
www.followuip.cc
www.followiup.cc
www.followu.cc
www.followuo.cc
www.followupo.cc
www.followuop.cc
www.followul.cc
www.followupl.cc
www.followulp.cc

followup.cc 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.

followup.cc 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.

FOLLOWUP.CC Followup Software

followup.cc Website Information

Advertisement

followup.cc Alexa Rank

followup.cc whois

followup.cc server information

Servers Location

followup.cc desktop page speed rank

followup.cc Desktop Speed Test Quick Summary

priority - 22Enable 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 211.7KiB (74% reduction).

priority - 14Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 7Leverage 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:

priority - 5Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 48.1KiB (46% reduction).

followup.cc Desktop Resource Breakdown

followup.cc mobile page speed rank

followup.cc Mobile Speed Test Quick Summary

priority - 48Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 30Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 293.9KiB (63% reduction).

priority - 20Enable 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 196.3KiB (88% reduction).

priority - 6Leverage 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:

priority - 3Minify 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 33.2KiB (16% reduction).

followup.cc Mobile Resource Breakdown

followup.cc mobile page usability

followup.cc Mobile Usability Test Quick Summary

priority - 14Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 606 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

followup.cc HTML validation

Errors

Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”.

Bad value “https://fonts.googleapis.com/css?family=Karla|Scope+One” for attribute “href” on element “link”: Illegal character in query: “|” is not allowed.

Duplicate ID “nav-pricing”.

Duplicate ID “install-button”.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)

Duplicate ID “Layer_1”.

Duplicate ID “Shape”.

Warnings

The first occurrence of ID “nav-pricing” was here.

The first occurrence of ID “install-button” was here.

The first occurrence of ID “Layer_1” was here.

The “name” attribute is obsolete. Consider putting an “id” attribute on the nearest container instead.

The first occurrence of ID “Shape” was here.

This document appears to be written in English. Consider adding “lang="en"” (or variant) to the “html” start tag.

followup.cc similar domains

followup.cc Ping

followup.cc TRACEROUTE