Peppermintweddings.Ca - Info receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in Houston, TX, 77092, United States and links to network IP address This server doesn't support HTTPS and doesn't support HTTP/2.

About -

How popular is

Daily Unique Visitors:
Monthly Unique Visitors:
Daily Pageviews:
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a (Percent of global Internet users)
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

Organic Keywords:
Organic Traffic:
Organic Cost:
Adwords Keywords:
Adwords Traffic:
Adwords Cost:


Domain Authority:
Page Authority:

Backlinks Report

Total Sites Linking In (Alexa):
Total Backlinks:
Follow Links:
Nofollow Links:
Referring Domains:
Referring IPs:

How socially engaged is

Google +:

How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is worth?

Website Value:

Where is hosted?

Server location
Server IP:
CyrusOne LLC 
Server Location:
United States

Other sites hosted on

How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights)

Suggestions Summary

Optimize images

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

Optimize the following images to reduce their size by 1.6MiB (62% reduction).

Compressing could save 154.7KiB (70% reduction).
Compressing could save 124.3KiB (73% reduction).
Compressing could save 121.9KiB (71% reduction).
Compressing could save 118.3KiB (70% reduction).
Compressing could save 115.1KiB (***% reduction).
Compressing could save 105.2KiB (***% reduction).
Compressing could save 104.2KiB (71% reduction).
Compressing could save 101.6KiB (73% reduction).
Compressing could save 93.9KiB (67% reduction).
Compressing could save 93KiB (72% reduction).
Compressing could save 91.4KiB (71% reduction).
Compressing could save 85KiB (72% reduction).
Compressing could save 81.5KiB (68% reduction).
Compressing could save 61.1KiB (68% reduction).
Compressing could save 35KiB (56% reduction).
Compressing could save 25.6KiB (19% reduction).
Compressing could save 12.2KiB (27% reduction).
Compressing could save 11.1KiB (27% reduction).
Compressing could save 9.6KiB (28% reduction).
Compressing could save 8.7KiB (29% reduction).
Compressing could save 8.3KiB (29% reduction).
Compressing could save 8.2KiB (29% reduction).
Compressing could save 6.7KiB (30% reduction).
Compressing could save 6.3KiB (32% reduction).
Compressing could save 4.1KiB (53% reduction).
Compressing could save 3.7KiB (52% reduction).
Compressing could save 3.7KiB (51% reduction).
Compressing could save 3.6KiB (51% reduction).
Compressing could save 3.5KiB (50% reduction).
Compressing could save 3.5KiB (50% reduction).
Compressing could save 3.3KiB (54% reduction).
Compressing could save 796B (65% reduction).
Compressing could save 764B (63% reduction).
Compressing could save 584B (33% reduction).
Compressing could save 580B (33% reduction).
Compressing could save 575B (33% reduction).
Compressing could save 560B (35% reduction).

Reduce server response time

In our test, your server responded in 0.48 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

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

Your page has 1 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.Optimize CSS Delivery of the following:

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 5.7KiB (25% reduction).

Minifying could save 3.6KiB (30% reduction) after compression.
Minifying could save 1.3KiB (15% reduction) after compression.
Minifying could save 849B (49% reduction) after compression.

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: (6 hours)

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.

The tap target <a href="https://www.fa…PeppermintWeds"></a> and 4 others are close to other tap targets .
The tap target <h1 class="menu-toggle">Menu</h1> is close to 1 other tap targets .
The tap target <a href="#content" class="skip-link screen-reader-text">Skip to content</a> is close to 1 other tap targets .

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 1.2KiB (18% reduction).

Minifying could save 1.2KiB (18% reduction) after compression.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Download optimized image, JavaScript, and CSS resources for this page.

Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

SSL Checker - SSL Certificate Verify does not support HTTPS
Verifying SSL Support. Please wait...

Verify HTTP/2 Support does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...

Site Categories (dmoz)

Currently Not Available

What sites are related to

There are no sites related

Http Header

HTTP/1.1 301 Moved Permanently
Server: nginx/1.12.0
Date: Wed, 13 Sep 2017 20:49:18 GMT
Content-Type: text/html; ch***t=UTF-8
Content-Length: 0
Connection: close
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Vary: Accept-Encoding
X-Endurance-Cache-Level: 2
X-Acc-Exp: 43200
X-Proxy-Cache: MISS
HTTP/1.1 200 OK
Date: Wed, 13 Sep 2017 20:49:18 GMT
Server: Apache
Link: ; rel="", ; rel=shortlink
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Vary: Accept-Encoding
X-Endurance-Cache-Level: 2
Connection: close
Content-Type: text/html; ch***t=UTF-8

DNS Lookup

Type Ip Target TTL
TXT 3600
TXT 3600
MX 3600
MX 3600
SOA 600
Serial Number 2017082202
Refresh 28800
Retry 7200
Expire 604800
Minimum TTL 0
A 3588
NS 3588
NS 3588

Whois Lookup

Domain Created:
Domain Age:

whois lookup at
Domain name:
Domain status: registered
Creation date: 2013/09/24
Expiry date: 2017/09/24
Updated date: 2017/08/22
DNSSEC: Unsigned

Name: Go Daddy Domains Canada, Inc
Number: 2316042

Name servers:

% WHOIS look-up made at 2017-09-13 20:49:26 (GMT)
% Use of CIRA's WHOIS service is governed by the Terms of Use in its Legal
% Notice, available at
% (c) 2017 Canadian Internet Registration Authority, (
Last update was 37 days ago
This can take up to 60 seconds. Please wait...

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget