10.4 sec in total
3.5 sec
6.5 sec
506 ms
Click here to check amazing Dougmcnish content for Canada. Otherwise, check out these important facts you probably never knew about dougmcnish.com
Visit dougmcnish.comWe analyzed Dougmcnish.com page load time and found that the first response time was 3.5 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
dougmcnish.com performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value14.2 s
0/100
25%
Value5.7 s
51/100
10%
Value2,170 ms
6/100
30%
Value0.001
100/100
15%
Value14.1 s
9/100
10%
3455 ms
82 ms
113 ms
114 ms
171 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 47% of them (41 requests) were addressed to the original Dougmcnish.com, 18% (16 requests) were made to Scontent.cdninstagram.com and 9% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Dougmcnish.com.
Page size can be reduced by 754.9 kB (20%)
3.8 MB
3.1 MB
In fact, the total size of Dougmcnish.com main page is 3.8 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. 60% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 59.0 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. This page needs HTML code to be minified as it can gain 11.5 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 59.0 kB or 87% of the original size.
Potential reduce by 70.2 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. Dougmcnish images are well optimized though.
Potential reduce by 338.3 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 338.3 kB or 70% of the original size.
Potential reduce by 287.5 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. Dougmcnish.com needs all CSS files to be minified and compressed as it can save up to 287.5 kB or 81% of the original size.
Number of requests can be reduced by 41 (55%)
74
33
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dougmcnish. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
dougmcnish.com
3455 ms
wp-emoji-release.min.js
82 ms
menu-image.css
113 ms
woocommerce-layout.css
114 ms
woocommerce.css
171 ms
pagenavi-css.css
153 ms
css
70 ms
genericons.css
165 ms
style.css
177 ms
custom.css
168 ms
jquery.js
201 ms
jquery-migrate.min.js
229 ms
add-to-cart.min.js
253 ms
woocommerce-add-to-cart.js
255 ms
style.css
259 ms
bootstrap.css
274 ms
bootstrap-responsive.css
264 ms
css-menu.css
307 ms
jquery.mmenu.all.css
333 ms
menu-styles.css
312 ms
font-awesome.min.css
4 ms
css
46 ms
css
58 ms
buttons.js
8 ms
jquery-1.9.1.min.js
386 ms
jquery.mmenu.min.js
385 ms
menu-scripts.js
385 ms
jquery.blockUI.min.js
404 ms
woocommerce.min.js
403 ms
jquery.cookie.min.js
415 ms
cart-fragments.min.js
426 ms
skip-link-focus-fix.js
427 ms
functions.js
447 ms
12317686_240448609631090_2003855748_n.jpg
582 ms
12317686_240448609631090_2003855748_n.jpg
659 ms
10693451_192913097749891_1119441940_n.jpg
676 ms
10693451_192913097749891_1119441940_n.jpg
619 ms
10296829_1692602954354908_1888273883_n.jpg
765 ms
10296829_1692602954354908_1888273883_n.jpg
642 ms
10375886_1563919903920097_2068787220_n.jpg
678 ms
10375886_1563919903920097_2068787220_n.jpg
663 ms
12784089_945881592175147_2133633921_n.jpg
989 ms
12784089_945881592175147_2133633921_n.jpg
739 ms
12816850_430345687164111_1133788738_n.jpg
879 ms
12816850_430345687164111_1133788738_n.jpg
730 ms
12825866_1582085225445700_2092744904_n.jpg
774 ms
12825866_1582085225445700_2092744904_n.jpg
859 ms
12825959_1052833381447161_1757653898_n.jpg
833 ms
12825959_1052833381447161_1757653898_n.jpg
810 ms
menus.png
314 ms
Nav-Drop-Down-Images-yoso.png
428 ms
slider-img.jpg
245 ms
person-img.jpg
197 ms
instragram-img.jpg
196 ms
Yoso-blog.png
501 ms
eat-real-food.png
413 ms
colouring-books.png
880 ms
sign.png
320 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
34 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
39 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
149 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
147 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
148 ms
serifa-bt.ttf
341 ms
fontawesome-webfont.woff
10 ms
b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf
157 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
145 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
143 ms
serifa-bt-bold.woff
426 ms
dougmcnish.com
2418 ms
getAllAppDefault.esi
230 ms
getSegment.php
154 ms
checkOAuth.esi
6 ms
t.dhj
6 ms
t.dhj
13 ms
cm
27 ms
s-3271.xgi
10 ms
hbpix
50 ms
10 ms
xrefid.xgi
5 ms
pixel
20 ms
12 ms
pixel
15 ms
2981
18 ms
index.a8fc48294ca4cc10eb440189d9f22d7c.html
14 ms
buttons.ab966a004186897711de4a5ed256c924.css
9 ms
st.125da8bfe70ad3e00a35a6e4c65d8bc5.js
3 ms
woocommerce-smallscreen.css
78 ms
dougmcnish.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
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
dougmcnish.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
dougmcnish.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dougmcnish.com 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 Dougmcnish.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.
dougmcnish.com
Open Graph description is not detected on the main page of Dougmcnish. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: