10.6 sec in total
3 sec
7.3 sec
398 ms
Click here to check amazing Whitebark Pine content. Otherwise, check out these important facts you probably never knew about whitebarkpine.ca
WPEF is a non-profit, science-based organization working to restore and preserve the whitebark pine and to educate the public on its valuable ecosystem.
Visit whitebarkpine.caWe analyzed Whitebarkpine.ca page load time and found that the first response time was 3 sec and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
whitebarkpine.ca performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value22.2 s
0/100
25%
Value19.8 s
0/100
10%
Value3,750 ms
1/100
30%
Value0.014
100/100
15%
Value24.9 s
0/100
10%
2954 ms
57 ms
111 ms
156 ms
158 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 77% of them (113 requests) were addressed to the original Whitebarkpine.ca, 19% (28 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Whitebarkpine.ca.
Page size can be reduced by 1.9 MB (23%)
8.3 MB
6.4 MB
In fact, the total size of Whitebarkpine.ca main page is 8.3 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. Only a small number of websites need less resources to load. Images take 6.8 MB which makes up the majority of the site volume.
Potential reduce by 142.2 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 142.2 kB or 83% of the original size.
Potential reduce by 1.4 MB
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. Obviously, Whitebark Pine needs image optimization as it can save up to 1.4 MB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 359.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 359.8 kB or 33% of the original size.
Potential reduce by 8.6 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. Whitebarkpine.ca has all CSS files already compressed.
Number of requests can be reduced by 97 (87%)
111
14
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whitebark Pine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
whitebarkpine.ca
2954 ms
style.min.css
57 ms
styles.css
111 ms
email-subscribers-public.css
156 ms
rs6.css
158 ms
jquery.socialfeed.css
157 ms
url-shortify.css
156 ms
style.css
156 ms
style.css
163 ms
plugins.min.css
207 ms
mediaelementplayer-legacy.min.css
220 ms
wp-mediaelement.min.css
218 ms
modules.min.css
275 ms
blog.min.css
224 ms
font-awesome.min.css
221 ms
style.min.css
260 ms
ionicons.min.css
267 ms
style.css
264 ms
style.css
271 ms
simple-line-icons.css
273 ms
dripicons.css
312 ms
modules-responsive.min.css
317 ms
blog-responsive.min.css
319 ms
style_dynamic_responsive.css
321 ms
style_dynamic.css
322 ms
js_composer.min.css
336 ms
css
46 ms
default.css
363 ms
formreset.min.css
370 ms
formsmain.min.css
371 ms
readyclass.min.css
377 ms
browsers.min.css
380 ms
pum-site-styles.css
387 ms
jquery.min.js
418 ms
jquery-migrate.min.js
422 ms
rbtools.min.js
441 ms
rs6.min.js
479 ms
css
40 ms
api.js
43 ms
codebird.js
423 ms
doT.min.js
392 ms
moment.min.js
372 ms
jquery.socialfeed.js
328 ms
en-ca.js
330 ms
url-shortify.js
346 ms
jquery.json.min.js
347 ms
gravityforms.min.js
436 ms
style.css
371 ms
placeholders.jquery.min.js
383 ms
hooks.min.js
399 ms
i18n.min.js
405 ms
index.js
402 ms
index.js
403 ms
email-subscribers-public.js
370 ms
core.min.js
361 ms
tabs.min.js
360 ms
accordion.min.js
447 ms
datepicker.min.js
448 ms
mediaelement-and-player.min.js
422 ms
mediaelement-migrate.min.js
411 ms
wp-mediaelement.min.js
404 ms
jquery.appear.js
405 ms
modernizr.custom.85257.js
405 ms
jquery.hoverIntent.min.js
404 ms
jquery.plugin.js
368 ms
jquery.countdown.min.js
365 ms
parallax.min.js
357 ms
select2.min.js
353 ms
easypiechart.js
349 ms
jquery.waypoints.min.js
349 ms
css
20 ms
Chart.min.js
405 ms
counter.js
378 ms
absoluteCounter.js
372 ms
fluidvids.min.js
366 ms
jquery.prettyPhoto.js
353 ms
jquery.nicescroll.min.js
351 ms
ScrollToPlugin.min.js
373 ms
TweenLite.min.js
371 ms
CSSPlugin.min.js
369 ms
EasePack.min.js
369 ms
jquery-scrollspy.js
2235 ms
jquery.mixitup.min.js
353 ms
jquery.multiscroll.min.js
304 ms
jquery.waitforimages.js
283 ms
jquery.infinitescroll.min.js
283 ms
jquery.easing.1.3.js
273 ms
skrollr.js
412 ms
slick.min.js
411 ms
jquery.touchpunch.min.js
2407 ms
jquery.flexslider-min.js
410 ms
TimelineLite.min.js
409 ms
isotope.pkgd.min.js
584 ms
packery-mode.pkgd.min.js
582 ms
modules.min.js
582 ms
blog.min.js
580 ms
js_composer_front.min.js
627 ms
like.js
662 ms
pum-site-scripts.js
662 ms
wp-polyfill.min.js
661 ms
index.js
668 ms
whitebark_final_logo_transparent_white.png
672 ms
whitebark_final_logo_black.jpg
667 ms
whitebark_final_logo_transparent.jpg
745 ms
Slide1.jpg
873 ms
Slide2.jpg
770 ms
Slide3.jpg
769 ms
AGM-2024-Announcement-1-1.jpg
992 ms
Pincher_bullcrop.png
912 ms
CanadaDay.jpg
870 ms
SpringClean2023.png
915 ms
WPEF-Logo-Horizontal-White.png
923 ms
ConfPic.jpg
187 ms
KFOlCnqEu92Fr1MmSU5fChc9.ttf
404 ms
KFOkCnqEu92Fr1MmgVxGIzc.ttf
421 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
420 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
422 ms
KFOlCnqEu92Fr1MmWUlfChc9.ttf
421 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
426 ms
ElegantIcons.woff
884 ms
Simple-Line-Icons.ttf
883 ms
u-4n0qyriQwlOrhSvowK_l52xwNZVsf_.ttf
425 ms
u-4n0qyriQwlOrhSvowK_l52_wFZVsf_.ttf
424 ms
u-440qyriQwlOrhSvowK_l5-ciZJ.ttf
424 ms
u-4n0qyriQwlOrhSvowK_l521wRZVsf_.ttf
424 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf
424 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf
462 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf
461 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf
458 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf
461 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf
461 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf
460 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf
463 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf
463 ms
fontawesome-webfont.woff
903 ms
ionicons.ttf
946 ms
KFOjCnqEu92Fr1Mu51S7ACc0CsE.ttf
462 ms
KFOkCnqEu92Fr1Mu51xGIzc.ttf
461 ms
KFOjCnqEu92Fr1Mu51TjASc0CsE.ttf
461 ms
KFOiCnqEu92Fr1Mu51QrEz4dKg.ttf
460 ms
KFOjCnqEu92Fr1Mu51TzBic0CsE.ttf
464 ms
KFOjCnqEu92Fr1Mu51TLBCc0CsE.ttf
462 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
95 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
93 ms
u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf
94 ms
recaptcha__en.js
145 ms
whitebarkpine.ca accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
whitebarkpine.ca 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
whitebarkpine.ca 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whitebarkpine.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Whitebarkpine.ca 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.
whitebarkpine.ca
Open Graph data is detected on the main page of Whitebark Pine. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: