4.9 sec in total
966 ms
3.5 sec
380 ms
Visit martock.com now to see the best up-to-date Martock content for Canada and also check out these interesting facts you probably never knew about martock.com
Visit martock.comWe analyzed Martock.com page load time and found that the first response time was 966 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
martock.com performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value20.1 s
0/100
25%
Value17.7 s
0/100
10%
Value2,670 ms
4/100
30%
Value0.177
68/100
15%
Value21.1 s
1/100
10%
966 ms
68 ms
130 ms
129 ms
131 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 22% of them (28 requests) were addressed to the original Martock.com, 26% (33 requests) were made to Scontent.cdninstagram.com and 7% (9 requests) were made to Btn.weather.ca. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Btn.weather.ca.
Page size can be reduced by 407.3 kB (25%)
1.6 MB
1.2 MB
In fact, the total size of Martock.com main page is 1.6 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 26.3 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 26.3 kB or 76% of the original size.
Potential reduce by 50.1 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. Martock images are well optimized though.
Potential reduce by 252.7 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 252.7 kB or 60% of the original size.
Potential reduce by 78.3 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. Martock.com needs all CSS files to be minified and compressed as it can save up to 78.3 kB or 79% of the original size.
Number of requests can be reduced by 58 (46%)
125
67
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Martock. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
martock.com
966 ms
dropdown.css
68 ms
default.css
130 ms
main4.css
129 ms
AC_RunActiveContent.js
131 ms
mobilecheck.js
131 ms
show_ads.js
7 ms
helper.css
67 ms
current.jpg
222 ms
56 ms
all.js
42 ms
template1.php
2171 ms
blueSQ.gif
500 ms
tl_brdr2_trans.gif
48 ms
embed
200 ms
ca-pub-9331117000386932.js
208 ms
zrt_lookup.html
202 ms
show_ads_impl.js
97 ms
spacer.gif
61 ms
tr_brdr2_trans.gif
90 ms
bl_brdr2_trans.gif
68 ms
br_brdr2_trans.gif
90 ms
safe_subscribe_logo.gif
62 ms
header-logo-bg2.jpg
93 ms
martock-logo.jpg
94 ms
top-neweStoreSPECIALS.jpg
94 ms
martock-topad.jpg
93 ms
menu-bg.jpg
93 ms
nav-arrow-down-white.png
180 ms
nav-arrow-right-white.png
184 ms
photos-bg.jpg
365 ms
mainpic-instagram.jpg
363 ms
FP-onTree_s1.jpg
364 ms
FP-wood-safetyad_s1.jpg
183 ms
2016%20-%202017%20Pass%20119.95%20.jpg
572 ms
FP-social-buttons-sm.jpg
363 ms
greenCIRCLE.gif
363 ms
blueSQ.gif
436 ms
bOVAL.gif
431 ms
March%20Break%20Camp%202016.jpg
696 ms
FP-mobile-buttonv3.png
464 ms
footer-partners.jpg
433 ms
red-rec.GIF
439 ms
combined.css
66 ms
smoothDivScroll.css
66 ms
stack_161235.js
199 ms
jquery.min.js
163 ms
jquery.cycle.lite.js
161 ms
301 ms
xd_arbiter.php
126 ms
xd_arbiter.php
269 ms
ads
268 ms
osd.js
63 ms
embed
266 ms
analytics.js
152 ms
stackpile.api-6712054ce0.js
177 ms
play_small.png
148 ms
11950535_599830806848789_797962930_n.jpg
320 ms
12816986_1214423851902853_1006360415_n.jpg
245 ms
12328292_1861761974050456_1752183813_n.jpg
301 ms
12797620_1516615685311833_203677579_n.jpg
300 ms
12822436_981986111893177_1502222396_n.jpg
299 ms
12822586_1111048158929498_1525724918_n.jpg
356 ms
12530843_257389777928265_1898245222_n.jpg
454 ms
12784079_1050654791623971_1014220739_n.jpg
365 ms
12798029_782774771854905_1759659928_n.jpg
362 ms
12826169_261264074205184_1461938993_n.jpg
364 ms
12383453_1190117464334855_1114217962_n.jpg
362 ms
12783455_1694662027484988_1265479569_n.jpg
367 ms
12797882_893457980752329_329179474_n.jpg
365 ms
12383506_1013477845384088_1290578910_n.jpg
365 ms
12783878_1734685070100823_1296473433_n.jpg
366 ms
12748447_764300820370076_1422263911_n.jpg
367 ms
12751077_1122914161073381_972077142_n.jpg
368 ms
12328097_488617007990384_1323147392_n.jpg
368 ms
12783330_810297802410295_1659318267_n.jpg
368 ms
12748350_1566808616968495_2114502641_n.jpg
368 ms
11349309_568601789975688_705850232_n.jpg
436 ms
12749814_1721377064816267_1724941771_n.jpg
434 ms
12749922_1571499473168842_236541862_n.jpg
434 ms
12728600_967277323350567_259859519_n.jpg
439 ms
12717127_935247146559479_764473424_n.jpg
437 ms
12750042_1054370421282564_1722006286_n.jpg
437 ms
12751177_235941480075632_226276155_n.jpg
450 ms
12750007_1073699362653026_877554369_n.jpg
449 ms
12716802_1691071597802710_18765537_n.jpg
450 ms
12728465_1267987036550824_561511948_n.jpg
448 ms
12748392_1507343842908622_1336280128_n.jpg
449 ms
12729512_998572660218031_329868182_n.jpg
464 ms
12750145_783828301749277_1631390538_n.jpg
464 ms
collect
24 ms
collect
147 ms
stackpile.api-6712054ce0.js
21 ms
m_js_controller.js
41 ms
abg.js
70 ms
0992f33945a94632a64d2587cfa6f814embedcompiled_fastui.css
38 ms
0992f33945a94632a64d2587cfa6f814embedcompiled__en.js
100 ms
client.js
171 ms
favicon
122 ms
googlelogo_color_112x36dp.png
113 ms
nessie_icon_tiamat_white.png
74 ms
s
67 ms
x_button_blue2.png
43 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
23 ms
cb=gapi.loaded_0
67 ms
postmessageRelay
60 ms
nr-885.min.js
44 ms
3193398744-postmessagerelay.js
48 ms
rpc:shindig_random.js
47 ms
a53393d12f
84 ms
cb=gapi.loaded_0
12 ms
logo-plus.png
35 ms
googlelogo_color_46x16dp.png
33 ms
blank.gif
16 ms
menu_arrow_open.gif
5 ms
combined_v22.png
26 ms
proxy.html
55 ms
cb=gapi.loaded_0
3 ms
events
328 ms
weatherbuttons.js
27 ms
wbtn_240x60.css
54 ms
counter.gif
120 ms
referer.gif
34 ms
logo.gif
51 ms
btn_alert_23460.gif
55 ms
en.gif
55 ms
swirl.gif
28 ms
search_en.gif
31 ms
martock.com accessibility score
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
button, link, and menuitem elements do not have accessible names.
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
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
martock.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
martock.com SEO score
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 Martock.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 Martock.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.
martock.com
Open Graph description is not detected on the main page of Martock. 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: