Breakersonthelake.Ca - Info breakersonthelake.ca

breakersonthelake.ca receives about 136 unique visitors and 272 (2.00 per visitor) page views per day which should earn about $1.11/day from advertising revenue. Estimated site value is $810.65. According to Alexa Traffic Rank breakersonthelake.ca is ranked number 6,509,976 in the world and 3.0E-6% of global Internet users visit it. Site is hosted in Provo, Utah, 84606, United States and links to network IP address 162.241.244.141. This server supports HTTPS and HTTP/2.

About - breakersonthelake.ca


Technologies used on Website

Web Servers
Apache

breakersonthelake.ca Profile

Title: Breakers Motel on the Lake :: Cobourg, ON
Description: Private sandy beach, minutes to downtown shopping and restaurants, modern non-smoking motel rooms, some with fireplaces, and housekeeping cottages.
Last update was 59 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with breakersonthelake.ca in any way. Only publicly available statistics data are displayed.

How popular is breakersonthelake.ca?

136 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
136
Monthly Unique Visitors:
3,264
Pages per Visit:
2.00
Daily Pageviews:
272
Alexa Rank:
6,509,976 visit alexa
Alexa Reach:
3.0E-6%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*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

SEMrush
Domain:
  breakersonthelake.ca
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is breakersonthelake.ca?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
breakersonthelake.ca
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
breakersonthelake.ca
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much breakersonthelake.ca can earn?

Daily Revenue:
$1.11
Monthly Revenue:
$33.30
Yearly Revenue:
$405.15
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do breakersonthelake.ca lose due to Adblock?

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

Daily revenue loss by country

Currently Not Available

How much is breakersonthelake.ca worth?

Website Value:
$810.65

+ Where is breakersonthelake.ca hosted?

Server IP:
162.241.244.141
ASN:
AS46606 
ISP:
Unified Layer 
Server Location:
Provo
Utah, UT
84606
United States, US
 

Other sites hosted on 162.241.244.141

+ How fast does breakersonthelake.ca load?

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

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://breakersonthelake.ca/
0 ms52 ms1 KB3 KB200text/htmlDocument
http://breakersonthelake.ca/indexlayout.jpg
63 ms111 ms283 KB283 KB200image/jpegImage
http://breakersonthelake.ca/greencanoe.png
64 ms246 ms55 KB55 KB200image/pngImage
http://breakersonthelake.ca/omsup%20logo.png
66 ms208 ms19 KB19 KB200image/pngImage
http://breakersonthelake.ca/Waves.mp3
106 ms237 ms0 KB0 KB200audio/mpegDocument
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAMAAAADACAYAAABS3GwHAAAAAXNSR0IArs4c6QAABqVJREFUeNrt3c
274 ms274 ms0 KB2 KB200image/pngImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAJwCAYAAABI9AvEAAACkklEQVRIS1XHdxQIZBiFcTtCkmRHqS
274 ms274 ms0 KB1 KB200image/pngImage
data:image/svg+xml;base64,PHN2ZyBmaWxsPSIjZmZmZmZmIiBoZWlnaHQ9IjI0IiB2aWV3Qm94PSIwIDAgMjQgMjQiIHdpZH
284 ms284 ms0 KB0 KB200image/svg+xmlImage
data:image/svg+xml;base64,PHN2ZyBmaWxsPSIjZmZmZmZmIiBoZWlnaHQ9IjI0IiB2aWV3Qm94PSIwIDAgMjQgMjQiIHdpZH
285 ms285 ms0 KB0 KB200image/svg+xmlImage
data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPHN2ZyB2ZXJzaW9uPSIxLj
287 ms287 ms0 KB0 KB200image/svg+xmlImage
http://breakersonthelake.ca/Waves.mp3
319 ms692 ms0 KB64 KB206audio/mpegMedia
data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IE
324 ms324 ms0 KB1 KB200image/svg+xmlImage
data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IE
326 ms326 ms0 KB1 KB200image/svg+xmlImage
Serve static assets with an efficient cache policy - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://breakersonthelake.ca/indexlayout.jpg
0 ms283 KB
http://breakersonthelake.ca/greencanoe.png
0 ms55 KB
http://breakersonthelake.ca/omsup%20logo.png
0 ms19 KB
http://breakersonthelake.ca/Waves.mp3
0 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
82 ms
7 ms
90 ms
6 ms
96 ms
32 ms
275 ms
42 ms
317 ms
6 ms
323 ms
24 ms
347 ms
17 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
164 ms3 ms2 ms
Properly size images - Potential savings of 43 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://breakersonthelake.ca/greencanoe.png
55 KB32 KB
http://breakersonthelake.ca/omsup%20logo.png
19 KB10 KB
Avoids enormous network payloads - Total size was 359 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://breakersonthelake.ca/indexlayout.jpg
283 KB
http://breakersonthelake.ca/greencanoe.png
55 KB
http://breakersonthelake.ca/omsup%20logo.png
19 KB
http://breakersonthelake.ca/
1 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
73 ms
Other
69 ms
Rendering
11 ms
Parse HTML & CSS
6 ms
Script Evaluation
3 ms
Script Parsing & Compilation
2 ms
Serve images in next-gen formats - Potential savings of 258 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://breakersonthelake.ca/indexlayout.jpg
283 KB220 KB
http://breakersonthelake.ca/greencanoe.png
55 KB38 KB
Avoids an excessive DOM size - 32 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
32
Maximum DOM Depth
5
Maximum Child Elements
7
Keep request counts low and transfer sizes small - 13 requests • 359 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
13359 KB
Image
10357 KB
Document
22 KB
Media
10 KB
Stylesheet
00 KB
Font
00 KB
Script
00 KB
Other
00 KB
Third-party
70 KB
Efficiently encode images - Potential savings of 169 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://breakersonthelake.ca/indexlayout.jpg
283 KB169 KB
Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 50 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 1230 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
319 ms10 ms5 ms
Avoids enormous network payloads - Total size was 359 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://breakersonthelake.ca/indexlayout.jpg
283 KB
http://breakersonthelake.ca/greencanoe.png
55 KB
http://breakersonthelake.ca/omsup%20logo.png
19 KB
http://breakersonthelake.ca/
1 KB
Minimizes main-thread work - 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Other
165 ms
Style & Layout
102 ms
Rendering
28 ms
Script Evaluation
10 ms
Parse HTML & CSS
9 ms
Script Parsing & Compilation
5 ms
Serve images in next-gen formats - Potential savings of 258 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://breakersonthelake.ca/indexlayout.jpg
283 KB220 KB
http://breakersonthelake.ca/greencanoe.png
55 KB38 KB
Avoids an excessive DOM size - 32 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
32
Maximum DOM Depth
5
Maximum Child Elements
7
Keep request counts low and transfer sizes small - 13 requests • 359 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
13359 KB
Image
10357 KB
Document
22 KB
Media
10 KB
Stylesheet
00 KB
Font
00 KB
Script
00 KB
Other
00 KB
Third-party
70 KB
Efficiently encode images - Potential savings of 169 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://breakersonthelake.ca/indexlayout.jpg
283 KB169 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://breakersonthelake.ca/
0 ms154 ms1 KB3 KB200text/htmlDocument
http://breakersonthelake.ca/indexlayout.jpg
162 ms454 ms283 KB283 KB200image/jpegImage
http://breakersonthelake.ca/greencanoe.png
163 ms414 ms55 KB55 KB200image/pngImage
http://breakersonthelake.ca/omsup%20logo.png
163 ms343 ms19 KB19 KB200image/pngImage
http://breakersonthelake.ca/Waves.mp3
177 ms520 ms0 KB0 KB200audio/mpegDocument
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAMAAAADACAYAAABS3GwHAAAAAXNSR0IArs4c6QAABqVJREFUeNrt3c
540 ms540 ms0 KB2 KB200image/pngImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAJwCAYAAABI9AvEAAACkklEQVRIS1XHdxQIZBiFcTtCkmRHqS
540 ms540 ms0 KB1 KB200image/pngImage
data:image/svg+xml;base64,PHN2ZyBmaWxsPSIjZmZmZmZmIiBoZWlnaHQ9IjI0IiB2aWV3Qm94PSIwIDAgMjQgMjQiIHdpZH
542 ms542 ms0 KB0 KB200image/svg+xmlImage
data:image/svg+xml;base64,PHN2ZyBmaWxsPSIjZmZmZmZmIiBoZWlnaHQ9IjI0IiB2aWV3Qm94PSIwIDAgMjQgMjQiIHdpZH
543 ms543 ms0 KB0 KB200image/svg+xmlImage
data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPHN2ZyB2ZXJzaW9uPSIxLj
544 ms544 ms0 KB0 KB200image/svg+xmlImage
http://breakersonthelake.ca/Waves.mp3
561 ms911 ms0 KB64 KB206audio/mpegMedia
data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IE
564 ms564 ms0 KB1 KB200image/svg+xmlImage
data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IE
565 ms565 ms0 KB1 KB200image/svg+xmlImage
Serve static assets with an efficient cache policy - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://breakersonthelake.ca/indexlayout.jpg
0 ms283 KB
http://breakersonthelake.ca/greencanoe.png
0 ms55 KB
http://breakersonthelake.ca/omsup%20logo.png
0 ms19 KB
http://breakersonthelake.ca/Waves.mp3
0 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
174 ms
5 ms
183 ms
8 ms
547 ms
18 ms
567 ms
12 ms
579 ms
8 ms
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 150 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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.

Try something…or at Breakers renders only 6 pixels tall (16 CSS pixels) .
BOOK NOW renders only 7 pixels tall (18 CSS pixels) .
www.omsup.ca renders only 6 pixels tall (16 CSS pixels) .
Site designed…maintained by renders only 4 pixels tall (10 CSS pixels) .
Bright Ideas renders only 4 pixels tall (10 CSS pixels) .

Optimize images

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

Optimize the following images to reduce their size by 200.5KiB (70% reduction).

Compressing http://breakersonthelake.ca/indexlayout.jpg could save 200.5KiB (70% reduction).

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.

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:

http://breakersonthelake.ca/greencanoe.png (expiration not specified)
http://breakersonthelake.ca/indexlayout.jpg (expiration not specified)
http://breakersonthelake.ca/omsup%20logo.png (expiration not specified)
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
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.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
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.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does breakersonthelake.ca use compression?

breakersonthelake.ca use gzip compression.
Original size: 2.58 KB
Compressed size: 1.1 KB
File reduced by: 1.48 KB (57%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

breakersonthelake.ca supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: adventuresinlandlording.ca
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Nov 15 18:46:19 2019 GMT
Valid until: Feb 13 18:46:19 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

breakersonthelake.ca supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Travel and Tourism/Lodging

+ Http Header

Upgrade: h2c
Connection: Upgrade

HTTP/2 200 
date: Thu, 01 Jan 1970 00:00:00 GMT
server: Apache
last-modified: Sun, 03 Jun 2018 01:22:23 GMT
accept-ranges: none
vary: Accept-Encoding
content-encoding: gzip
content-length: 1126
content-type: text/html

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
NS ns2.bluehost.com 3600
NS ns1.bluehost.com 3600

+ Whois Lookup

Domain Created:
2009-12-12
Domain Age:
10 years 17 days  
WhoIs:
 

whois lookup at whois.cira.ca...
Domain Name: breakersonthelake.ca
Registry Domain ID: D116***31-CIRA
Registrar WHOIS Server: whois.ca.fury.ca
Registrar URL: http://domainhelp.tucows.com
Updated Date: 2019-11-27T12:27:51Z
Creation Date: 2009-12-12T17:24:42Z
Registry Expiry Date: 2020-12-12T05:00:00Z
Registrar: Tucows.com Co.
Registrar IANA ID:
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: ON
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: REDACTED FOR PRIVACY
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State/Province: REDACTED FOR PRIVACY
Billing Postal Code: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Phone Ext: REDACTED FOR PRIVACY
Billing Fax: REDACTED FOR PRIVACY
Billing Fax Ext: REDACTED FOR PRIVACY
Billing Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Name Server: ns1.bluehost.com
Name Server: ns2.bluehost.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-12-29T12:14:17Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

%
% Use of CIRA's WHOIS service is governed by the Terms of Use in its Legal
% Notice, available at http://www.cira.ca/legal-notice/?lang=en
%
% (c) 2019 Canadian Internet Registration Authority, (http://www.cira.ca/)
Last update was 59 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with breakersonthelake.ca in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

tv.tvzon.tv
25 secs
kvfatehgarhsahib.com
44 secs
fastgo.in
57 secs
kventerprises.net
1 min
businessnewsthisweek.com
1 min
***s2.com
2 mins
***osveta.net
2 mins
20.epiciptv.com
2 mins
uk1024.net
2 mins
kveda.com
2 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

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) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
breakersonthelake.ca widget