4.2 sec in total
763 ms
2.5 sec
949 ms
Welcome to whitepoint.com homepage info - get ready to check White Point best content for Canada right away, or after learning these important things about whitepoint.com
For more than 90 years, White Point Beach Resort has been welcoming guests to Nova Scotia's South Shore. Stay, play, and get away from the every day.
Visit whitepoint.comWe analyzed Whitepoint.com page load time and found that the first response time was 763 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
whitepoint.com performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value5.9 s
14/100
25%
Value11.3 s
5/100
10%
Value4,110 ms
1/100
30%
Value0.115
86/100
15%
Value22.1 s
1/100
10%
763 ms
105 ms
52 ms
54 ms
84 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 71% of them (60 requests) were addressed to the original Whitepoint.com, 11% (9 requests) were made to Use.typekit.net and 4% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (859 ms) belongs to the original domain Whitepoint.com.
Page size can be reduced by 869.1 kB (22%)
3.9 MB
3.0 MB
In fact, the total size of Whitepoint.com main page is 3.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 115.5 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 115.5 kB or 76% of the original size.
Potential reduce by 37.9 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. White Point images are well optimized though.
Potential reduce by 592.8 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 592.8 kB or 69% of the original size.
Potential reduce by 122.9 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Whitepoint.com needs all CSS files to be minified and compressed as it can save up to 122.9 kB or 70% of the original size.
Number of requests can be reduced by 41 (56%)
73
32
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of White Point. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.whitepoint.com
763 ms
320.css
105 ms
480.css
52 ms
640.css
54 ms
768.css
84 ms
960.css
80 ms
1280.css
78 ms
surface_landscape.css
86 ms
dashicons.min.css
165 ms
thickbox.css
108 ms
jquery.fancybox.css
473 ms
checkbox.min.css
108 ms
flexslider.css
112 ms
jquery.fancybox.css
115 ms
jquery-ui.min.css
117 ms
jquery.min.js
31 ms
jquery.fancybox.js
859 ms
modernizr-2.6.2.min.js
164 ms
addthis_widget.js
28 ms
js
70 ms
jsapi
51 ms
dgs2ikq.js
172 ms
wp-emoji-release.min.js
41 ms
background-page-repeat.jpg
91 ms
thickbox.js
30 ms
main.js
30 ms
jquery-ui.min.js
55 ms
virtualtour.js
58 ms
jquery.flexslider-min.js
59 ms
jquery.fancybox.pack.js
68 ms
count.js
82 ms
sidebarv2.js
170 ms
www.whitepoint.com
194 ms
background-page-top.jpg
52 ms
logo.png
55 ms
Fireplace-at-White-Point-Beach-Resort.jpg
309 ms
Whitepointsnowfrombeach-1600x700.jpg
285 ms
golfheaderweb-copy-1600x700.jpg
284 ms
surfers.jpg
307 ms
WhitePointBeach-1600x700.jpg
370 ms
brfstbuffet-532x475.jpg
280 ms
Dogretreat-532x475.jpg
284 ms
brushwithgoodcheer-532x475.png
334 ms
retreat-callout-1600x630.jpg
368 ms
golfcourseair-1600x630.jpg
416 ms
DarkSkyReidSandbelt-532x475.jpg
368 ms
quilt.jpg
365 ms
ColouringontheCoast-532x475.jpg
364 ms
naturewalk-800x475.jpg
428 ms
to-do-callout-2-532x475.jpg
415 ms
bonfire-532x475.jpg
429 ms
swimmers-532x475.jpg
478 ms
gift-card.png
427 ms
icon-umbrella-medium.png
427 ms
gtm.js
143 ms
icon-double-arrows.png
280 ms
background-callout-overlay.png
332 ms
background-home-events.png
356 ms
icon-social-sprite.png
335 ms
count.js
103 ms
300lo.json
60 ms
loadingAnimation.gif
201 ms
icon-umbrella-small-red.png
199 ms
icon-umbrella-small.png
229 ms
icon-slider-arrow-previous.png
229 ms
icon-slider-arrow-next.png
229 ms
icon-arrow-down.png
228 ms
icon-double-arrows-blue.png
228 ms
SnoACFO-iqXyR-kNIzTCt_LpCucQZpQ2FVUupaJ5umMffH0qgsMmeMJ6Mk6f5MX.woff
45 ms
VCo3Nsg8I-Om2fVYbwXZDRxLBNcIlUorN-rdXeM_FUSffHkqgsMmeMJ6Mk6f5Mb.woff
76 ms
g57tMHtWHqi3VBW4yWNcZQHLQ9rUx_HZ4BTk8GoaZCMffH7qgsMmeMJ6Mk6f5Mw.woff
220 ms
0rIprtHS3gOP6_fOOSgGkX-Efz5NcVerzEHoZVRf4-3ffOeqgsMmeMJ6Mk6f5MS.woff
194 ms
dw9FLHzpaq3ri_Q2fEKjE4vhbK5mPCqEMrNdm6R8l09ffH7DggMmeMJ6Mk6f5gJ.woff
189 ms
AfBuCD1jQpCiwKy80Z4olVvGZYUBK3IT_az6iFzHXGwffwfDggMmeMJ6Mk6f5gI.woff
188 ms
wJXuRNOZQSYCD3ClQV-F_zNCOX-jTUuCCF2Ibz5rf3wffOEDggMmeMJ6Mk6f5Mt.woff
188 ms
sh.8e5f85691f9aaa082472a194.html
37 ms
analytics.js
30 ms
collect
52 ms
collect
139 ms
layers.e5ea973510bf60b3db41.js
18 ms
ga-audiences
20 ms
surface_portrait.css
29 ms
p.gif
123 ms
print.css
34 ms
whitepoint.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
whitepoint.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
whitepoint.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whitepoint.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Whitepoint.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
whitepoint.com
Open Graph data is detected on the main page of White Point. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: