nappy.co Website Information
Daily Unique Visits: 13,159
Daily Page Views: 65,795
Income Per Day: $164
Estimated Value: $98,400
nappy.co is registered under .CO top-level domain. Please check other sites in .CO zone.
No name server records were found.
and is probably hosted by AS-CHOOPA - Choopa, LLC, US. See the full list of other websites hosted by AS-CHOOPA - Choopa, LLC, US.
The highest website nappy.co position in Alexa rank database was 19215 and the lowest rank position was 996344. Current position of nappy.co in Alexa rank database is 103545.
Desktop speed score of nappy.co (38/100) is better than the results of 13.38% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of nappy.co (98/100) is better than the results of 55.61% of other sites and means that the page is mobile-friendly.
Mobile speed score of nappy.co (37/100) is better than the results of 15.74% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
nappy.co 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.
nappy.co 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.
nappy.co server information
Servers Location
nappy.co desktop page speed rank
Last tested: 2019-03-29
nappy.co Desktop Speed Test Quick Summary
priority - 113Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1.1MiB (53% reduction).
Compressing and resizing https://media.istockphoto.com/photos/large-group-o…e_JByqoYjH0eWni0rzvOo= could save 134.5KiB (93% reduction).
Compressing and resizing https://media.istockphoto.com/photos/multiethnic-f…ZC59EG2jmTSx6ELnJhKeY= could save 107.3KiB (93% reduction).
Compressing and resizing https://media.istockphoto.com/photos/girlfriends-e…huTpXqHmaOpiOjcyobfmQ= could save 104KiB (93% reduction).
Compressing and resizing https://media.istockphoto.com/photos/these-cramps-…lqvnawwnCYddAMptTSdOA= could save 98.3KiB (94% reduction).
Compressing and resizing https://media.istockphoto.com/photos/happy-african…Z5xCbiIqzQUs0vrDQ0NqQ= could save 88.5KiB (92% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/01/7Z8A0473-1024x683.jpg could save 35.6KiB (32% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/05/violonista_4-1024x647.jpg could save 33.6KiB (30% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/08/DSC_0096-678x1024.jpg could save 33KiB (24% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/05/DSC3726-678x1024.jpg could save 31.2KiB (24% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/01/7Z8A0008-A-683x1024.jpg could save 30.8KiB (28% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/07/7Z8A0113-1024x683.jpg could save 22.4KiB (23% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/04/7Z8A0326-683x1024.jpg could save 17.6KiB (22% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/03/FullSizeRender.jpg could save 17.4KiB (22% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/05/aline-1-1024x678.jpg could save 16.7KiB (16% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/04/7Z8A0697-1024x683.jpg could save 11.8KiB (13% reduction).
Compressing https://www.nappy.co/wp-content/themes/nappy/img/misc/navigation-menu.png could save 834B (80% reduction).
priority - 22Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 24 blocking script resources and 16 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://www.nappy.co/wp-includes/js/jquery/jquery.js?ver=1.12.4
https://www.nappy.co/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
https://www.nappy.co/wp-includes/js/mediaelement/m…n.js?ver=4.2.6-78496d1
https://www.nappy.co/wp-includes/js/mediaelement/m…grate.min.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/modernizr.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/respond.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/flexslider.js?ver=5.1.1
https://www.nappy.co/wp-includes/js/mediaelement/w…ement.min.js?ver=5.1.1
https://www.nappy.co/wp-content/plugins/contact-fo…s/scripts.js?ver=5.0.5
https://s0.wp.com/wp-content/js/devicepx-jetpack.js?ver=201913
https://www.nappy.co/wp-content/plugins/submit-pic…in/css/semantic.min.js
https://www.nappy.co/wp-content/plugins/submit-pic…in/js/jquery.custom.js
https://secure.gravatar.com/js/gprofiles.js?ver=2019Maraa
https://www.nappy.co/wp-content/plugins/jetpack/mo…s/wpgroho.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy-child…croll.min.js?ver=5.1.1
https://www.nappy.co/wp-includes/js/jquery/ui/core.min.js?ver=1.11.4
https://www.nappy.co/wp-content/themes/nappy-child/js/main.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/magnific-popup.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/scrollbar.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/waypoints.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/fitvids.js?ver=5.1.1
https://www.nappy.co/wp-content/plugins/bj-lazy-lo…lazy-load.min.js?ver=2
https://www.nappy.co/wp-includes/js/wp-embed.min.js?ver=5.1.1
Optimize CSS Delivery of the following:
https://www.nappy.co/wp-includes/css/dist/block-li…tyle.min.css?ver=5.1.1
https://www.nappy.co/wp-content/plugins/contact-fo…s/styles.css?ver=5.0.5
https://www.nappy.co/wp-content/plugins/submit-pic…s/styles.css?ver=5.1.1
https://www.nappy.co/wp-content/plugins/submit-pic…ntic.min.css?ver=5.1.1
https://fonts.googleapis.com/css?family=Lato:400,7…700italic&subset=latin
https://www.nappy.co/wp-content/themes/nappy/css/plugin.css
https://www.nappy.co/wp-content/themes/nappy-child/style.css?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/style.css
https://fonts.googleapis.com/css?family=Montserrat:400,400i,500,700
https://www.nappy.co/wp-content/themes/nappy/css/font.css
https://fonts.googleapis.com/css?family=Montserrat…as+Neue&ver=1496799461
https://www.nappy.co/wp-content/plugins/jetpack/css/jetpack.css?ver=6.8
https://secure.gravatar.com/dist/css/hovercard.min.css?ver=2019Maraa
https://secure.gravatar.com/dist/css/services.min.css?ver=2019Maraa
https://downloads.mailchimp.com/css/signup-forms/popup/1.0/modal.css
priority - 20Reduce server response time
In our test, your server responded in 2.2 seconds.
priority - 15Enable 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 149.2KiB (66% reduction).
Compressing https://downloads.mailchimp.com/js/signup-forms/popup/1.0/popup.js could save 66.5KiB (69% reduction).
Compressing https://downloads.mailchimp.com/css/signup-forms/popup/1.0/modal.css could save 914B (60% reduction).
Compressing https://downloads.mailchimp.com/css/signup-forms/popup/1.0/layout-2.css could save 533B (60% reduction).
Compressing https://downloads.mailchimp.com/css/signup-forms/popup/1.0/banner.css could save 364B (51% reduction).
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:
https://s3.amazonaws.com/downloads.mailchimp.com/j…p-forms/popup/embed.js (expiration not specified)
https://static.hotjar.com/c/hotjar-592662.js?sv=5 (60 seconds)
https://mc.us16.list-manage.com/subscribe/form-set…s.dojo_request_script0 (4.7 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 2Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 1Minify 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 5.8KiB (25% reduction).
Minifying https://www.nappy.co/wp-content/themes/nappy/style.css could save 1.5KiB (22% reduction) after compression.
Minifying https://www.nappy.co/wp-content/themes/nappy-child/style.css?ver=5.1.1 could save 563B (27% reduction) after compression.
priority - 1Minify 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 4.9KiB (32% reduction).
Minifying https://www.nappy.co/wp-content/themes/nappy/js/respond.js?ver=5.1.1 could save 1.5KiB (40% reduction) after compression.
Minifying https://www.nappy.co/wp-content/plugins/contact-fo…s/scripts.js?ver=5.0.5 could save 659B (17% reduction) after compression.
Minifying https://www.nappy.co/wp-content/themes/nappy/js/fitvids.js?ver=5.1.1 could save 427B (33% reduction) after compression.
Minifying https://www.nappy.co/wp-content/plugins/submit-pic…in/js/jquery.custom.js could save 109B (23% reduction) after compression.
nappy.co Desktop Resource Breakdown
Total Resources | 108 |
Number of Hosts | 18 |
Static Resources | 100 |
JavaScript Resources | 32 |
CSS Resources | 19 |
nappy.co mobile page speed rank
Last tested: 2019-03-29
nappy.co Mobile Speed Test Quick Summary
priority - 88Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 24 blocking script resources and 15 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://www.nappy.co/wp-includes/js/jquery/jquery.js?ver=1.12.4
https://www.nappy.co/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
https://www.nappy.co/wp-includes/js/mediaelement/m…n.js?ver=4.2.6-78496d1
https://www.nappy.co/wp-includes/js/mediaelement/m…grate.min.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/modernizr.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/respond.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/flexslider.js?ver=5.1.1
https://www.nappy.co/wp-includes/js/mediaelement/w…ement.min.js?ver=5.1.1
https://www.nappy.co/wp-content/plugins/contact-fo…s/scripts.js?ver=5.0.5
https://s0.wp.com/wp-content/js/devicepx-jetpack.js?ver=201913
https://www.nappy.co/wp-content/plugins/submit-pic…in/css/semantic.min.js
https://www.nappy.co/wp-content/plugins/submit-pic…in/js/jquery.custom.js
https://secure.gravatar.com/js/gprofiles.js?ver=2019Maraa
https://www.nappy.co/wp-content/plugins/jetpack/mo…s/wpgroho.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy-child…croll.min.js?ver=5.1.1
https://www.nappy.co/wp-includes/js/jquery/ui/core.min.js?ver=1.11.4
https://www.nappy.co/wp-content/themes/nappy-child/js/main.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/magnific-popup.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/scrollbar.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/waypoints.js?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/js/fitvids.js?ver=5.1.1
https://www.nappy.co/wp-content/plugins/bj-lazy-lo…lazy-load.min.js?ver=2
https://www.nappy.co/wp-includes/js/wp-embed.min.js?ver=5.1.1
Optimize CSS Delivery of the following:
https://www.nappy.co/wp-includes/css/dist/block-li…tyle.min.css?ver=5.1.1
https://www.nappy.co/wp-content/plugins/contact-fo…s/styles.css?ver=5.0.5
https://www.nappy.co/wp-content/plugins/submit-pic…s/styles.css?ver=5.1.1
https://www.nappy.co/wp-content/plugins/submit-pic…ntic.min.css?ver=5.1.1
https://fonts.googleapis.com/css?family=Lato:400,7…700italic&subset=latin
https://www.nappy.co/wp-content/themes/nappy/css/plugin.css
https://www.nappy.co/wp-content/themes/nappy-child/style.css?ver=5.1.1
https://www.nappy.co/wp-content/themes/nappy/style.css
https://fonts.googleapis.com/css?family=Montserrat:400,400i,500,700
https://www.nappy.co/wp-content/themes/nappy/css/font.css
https://fonts.googleapis.com/css?family=Montserrat…as+Neue&ver=1496799461
https://www.nappy.co/wp-content/plugins/jetpack/css/jetpack.css?ver=6.8
https://secure.gravatar.com/dist/css/hovercard.min.css?ver=2019Maraa
https://secure.gravatar.com/dist/css/services.min.css?ver=2019Maraa
priority - 50Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 488.6KiB (45% reduction).
Compressing https://media.istockphoto.com/photos/multiethnic-f…ZC59EG2jmTSx6ELnJhKeY= could save 77.1KiB (67% reduction).
Compressing https://media.istockphoto.com/photos/girlfriends-e…huTpXqHmaOpiOjcyobfmQ= could save 75KiB (67% reduction).
Compressing https://media.istockphoto.com/photos/these-cramps-…lqvnawwnCYddAMptTSdOA= could save 69.4KiB (66% reduction).
Compressing https://media.istockphoto.com/photos/happy-african…Z5xCbiIqzQUs0vrDQ0NqQ= could save 65.8KiB (69% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/03/7Z8A0491-1024x683.jpg could save 36.7KiB (24% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/02/7Z8A0444-1024x683.jpg could save 33.6KiB (26% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/04/7Z8A0060-1024x683.jpg could save 18.6KiB (19% reduction).
Compressing https://www.nappy.co/wp-content/uploads/2018/05/ab…9554-Pray-819x1024.jpg could save 17KiB (13% reduction).
Compressing https://www.nappy.co/wp-content/themes/nappy/img/misc/navigation-menu.png could save 834B (80% reduction).
priority - 31Reduce server response time
In our test, your server responded in 2.2 seconds.
priority - 8Enable 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 80.9KiB (64% reduction).
priority - 8Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 3Leverage 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://static.hotjar.com/c/hotjar-592662.js?sv=5 (60 seconds)
https://mc.us16.list-manage.com/subscribe/form-set…s.dojo_request_script0 (5 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 1Minify 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 5.8KiB (25% reduction).
Minifying https://www.nappy.co/wp-content/themes/nappy/style.css could save 1.5KiB (22% reduction) after compression.
Minifying https://www.nappy.co/wp-content/themes/nappy-child/style.css?ver=5.1.1 could save 563B (27% reduction) after compression.
priority - 1Minify 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 4.9KiB (32% reduction).
Minifying https://www.nappy.co/wp-content/themes/nappy/js/respond.js?ver=5.1.1 could save 1.5KiB (40% reduction) after compression.
Minifying https://www.nappy.co/wp-content/plugins/contact-fo…s/scripts.js?ver=5.0.5 could save 659B (17% reduction) after compression.
Minifying https://www.nappy.co/wp-content/themes/nappy/js/fitvids.js?ver=5.1.1 could save 427B (33% reduction) after compression.
Minifying https://www.nappy.co/wp-content/plugins/submit-pic…in/js/jquery.custom.js could save 109B (23% reduction) after compression.
nappy.co Mobile Resource Breakdown
Total Resources | 103 |
Number of Hosts | 17 |
Static Resources | 95 |
JavaScript Resources | 32 |
CSS Resources | 15 |
nappy.co mobile page usability
Last tested: 2019-03-29
nappy.co Mobile Usability Test Quick Summary
priority - 1Size 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.
<div class="logo">nappy</div>
is close to 1 other tap targets.<a href="https://www.nappy.co">nappy</a>
is close to 1 other tap targets.nappy.co HTML validation
Errors
Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.
"...</script> <link rel='https://api.w.org/' href='https://www.nappy.co/wp-json/' /> <link..."
Bad value “mailto:hi@nappy.co?subject=Hey nappy fam!” for attribute “href” on element “a”: Illegal character in query: space is not allowed.
"...s="title"><a style="color:#000; text-decoration:none;" href="mailto:hi@nappy.co?subject=Hey nappy fam!">HI@NAP..."
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
"...nter"> <img src="https://www.nappy.co/wp-content/themes/nappy/img/spinner_gif.gif"> </d..."
Warnings
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
"...ction --> <section class="work" id="work"> <div..."
nappy.co similar domains
www.nappy.net
www.nappy.org
www.nappy.info
www.nappy.biz
www.nappy.us
www.nappy.mobi
www.appy.co
www.nappy.co
www.bappy.co
www.nbappy.co
www.bnappy.co
www.happy.co
www.nhappy.co
www.hnappy.co
www.jappy.co
www.njappy.co
www.jnappy.co
www.mappy.co
www.nmappy.co
www.mnappy.co
www.nppy.co
www.nqppy.co
www.naqppy.co
www.nqappy.co
www.nwppy.co
www.nawppy.co
www.nwappy.co
www.nsppy.co
www.nasppy.co
www.nsappy.co
www.nzppy.co
www.nazppy.co
www.nzappy.co
www.napy.co
www.naopy.co
www.napopy.co
www.naoppy.co
www.nalpy.co
www.naplpy.co
www.nalppy.co
www.napoy.co
www.nappoy.co
www.naply.co
www.napply.co
www.napp.co
www.nappt.co
www.nappyt.co
www.nappty.co
www.nappg.co
www.nappyg.co
www.nappgy.co
www.napph.co
www.nappyh.co
www.napphy.co
www.nappu.co
www.nappyu.co
www.nappuy.co
nappy.co 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.
nappy.co 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.