4.6 sec in total
233 ms
3.9 sec
489 ms
Welcome to merkko.com homepage info - get ready to check Merkko best content right away, or after learning these important things about merkko.com
Established in 1987, we are an independently run business with an ethos of supplying the best quality goods and un-matched service. Grant & Stone has flourished to quickly become recognised as one of ...
Visit merkko.comWe analyzed Merkko.com page load time and found that the first response time was 233 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
merkko.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value18.3 s
0/100
25%
Value9.1 s
14/100
10%
Value630 ms
47/100
30%
Value0.004
100/100
15%
Value19.9 s
2/100
10%
233 ms
736 ms
83 ms
258 ms
248 ms
Our browser made a total of 182 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Merkko.com, 91% (166 requests) were made to Grantandstone.co.uk and 2% (4 requests) were made to Cdn.icomoon.io. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Grantandstone.co.uk.
Page size can be reduced by 653.0 kB (19%)
3.4 MB
2.7 MB
In fact, the total size of Merkko.com main page is 3.4 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.3 MB which makes up the majority of the site volume.
Potential reduce by 169.4 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 61.0 kB, which is 32% 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 169.4 kB or 90% of the original size.
Potential reduce by 191.6 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. Merkko images are well optimized though.
Potential reduce by 187.2 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 187.2 kB or 31% of the original size.
Potential reduce by 104.8 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. Merkko.com needs all CSS files to be minified and compressed as it can save up to 104.8 kB or 47% of the original size.
Number of requests can be reduced by 137 (78%)
175
38
The browser has sent 175 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Merkko. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 112 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
merkko.com
233 ms
www.grantandstone.co.uk
736 ms
calendar.css
83 ms
styles.css
258 ms
styles.css
248 ms
owl.carousel.min.css
249 ms
animate.css
251 ms
fontawesome5.css
254 ms
mgz_font.css
249 ms
mgz_bootstrap.css
329 ms
openiconic.min.css
331 ms
styles.css
332 ms
common.css
331 ms
styles.css
335 ms
magnific.css
335 ms
styles.css
413 ms
photoswipe.css
410 ms
default-skin.css
411 ms
blueimp-gallery.min.css
415 ms
styles.css
416 ms
flexslider.min.css
415 ms
trustpilot.min.css
492 ms
blog-m.css
492 ms
blog-new.css
493 ms
blog-custom.css
494 ms
require.js
500 ms
mixins.js
499 ms
requirejs-config.js
573 ms
guest_wishlist_modulejs.js
579 ms
cookiebot.js
582 ms
js
100 ms
markerclusterer.js
83 ms
prommt.min.js
311 ms
style-cf.css
18 ms
style.css
107 ms
prommt.min.css
310 ms
style.css
132 ms
markerclusterer.js
33 ms
jquery.mobile.custom.js
94 ms
common.js
93 ms
dataPost.js
93 ms
bootstrap.js
92 ms
fbevents.js
86 ms
gtm.js
169 ms
tp.widget.bootstrap.min.js
74 ms
tp.min.js
83 ms
grantandstone_logo.png
123 ms
buildit-logo.png
123 ms
DW-Burns-PM-logo-Blue-_RGB_-transparent_1.png
167 ms
chandlers.png
167 ms
chandlers_roofing.png
320 ms
CRS.png
167 ms
devondale-logo.png
168 ms
dougfield-logo_1.png
246 ms
fairalls.png
238 ms
grant-stone-1_1.png
238 ms
independent_roofing_supplies.png
321 ms
kent-blaxill.png
245 ms
MERKO.png
320 ms
ms-roofing_1.png
320 ms
parker.png
326 ms
pennyhill_timber.png
327 ms
rgb-logo.png
400 ms
roofing-gear.png
401 ms
SPS.png
403 ms
stamco_hoppings_2.png
403 ms
total-logo.png
407 ms
trading_depot_1.png
407 ms
awebb-transparent.png
482 ms
bmf_2.png
483 ms
payment_logos.png
485 ms
jquery.js
573 ms
es6-collections.js
493 ms
FormData.js
487 ms
form-key-provider.js
561 ms
mage-translation-dictionary.js
561 ms
main.js
562 ms
theme.js
565 ms
uc.js
154 ms
kick-icons.ttf
107 ms
grantstone.ttf
142 ms
modal.js
503 ms
domReady.js
570 ms
jquery.js
571 ms
jquery-mixin.js
572 ms
HelveticaNeue-CondensedBold.woff
622 ms
template.js
538 ms
confirm.js
496 ms
widget.js
566 ms
main.js
566 ms
bootstrap.js
564 ms
mfblogunveil.js
504 ms
weltpixel_persistentlayer.js
511 ms
weltpixel_gtm.js
569 ms
jquery.waypoints.js
569 ms
customer-data.js
498 ms
customer-data-mixin.js
503 ms
GRANTANDSTONE_MARKETING-1_1.jpg
835 ms
Web_Banner_G_S.jpg
668 ms
Web_Banner_G_S_1.jpg
734 ms
timber-merchants-banner.jpg
1063 ms
g_s-kitchen-img_1.jpg
497 ms
GandS-New-Lorry-at-Hemel_home.jpeg
504 ms
text.js
414 ms
smart-keyboard-handler.js
416 ms
mage.js
489 ms
ie-class-fixer.js
497 ms
underscore.js
493 ms
key-codes.js
560 ms
core.js
563 ms
translate.js
571 ms
wrapper.js
506 ms
knockout.js
580 ms
knockout-es5.js
494 ms
scripts.js
499 ms
engine.js
500 ms
bootstrap.js
502 ms
observable_array.js
572 ms
bound-nodes.js
583 ms
local.js
564 ms
registry.js
565 ms
section-config.js
575 ms
url.js
579 ms
storage.js
582 ms
jquery.storageapi.extended.js
585 ms
js-translation.json
420 ms
modal-popup.html
488 ms
modal-slide.html
490 ms
modal-custom.html
494 ms
knockout-repeat.js
239 ms
knockout-fast-foreach.js
243 ms
observable_source.js
242 ms
renderer.js
311 ms
console-logger.js
312 ms
resizable.js
315 ms
i18n.js
319 ms
scope.js
321 ms
range.js
322 ms
mage-init.js
391 ms
keyboard.js
391 ms
optgroup.js
395 ms
after-render.js
398 ms
autoselect.js
402 ms
datepicker.js
402 ms
outer_click.js
471 ms
fadeVisible.js
472 ms
collapsible.js
476 ms
staticChecked.js
479 ms
simple-checked.js
482 ms
bind-html.js
482 ms
tooltip.js
552 ms
color-picker.js
492 ms
events.js
484 ms
main.js
487 ms
jquery.cookie.js
410 ms
jquery.storageapi.min.js
413 ms
class.js
399 ms
loader.js
325 ms
async.js
328 ms
resizable.js
332 ms
logger.js
334 ms
entry-factory.js
335 ms
console-output-handler.js
405 ms
formatter.js
405 ms
message-pool.js
409 ms
levels-pool.js
412 ms
logger-utils.js
414 ms
tooltip.html
176 ms
spectrum.js
248 ms
tinycolor.js
246 ms
arrays.js
240 ms
compare.js
242 ms
misc.js
244 ms
objects.js
246 ms
strings.js
318 ms
template.js
318 ms
mouse.js
242 ms
dom-observer.js
245 ms
bindings.js
247 ms
entry.js
243 ms
moment.js
248 ms
print.css
82 ms
merkko.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
[role]s do not have all required [aria-*] attributes
[aria-*] attributes do not have valid values
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.
merkko.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
Page has valid source maps
merkko.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Merkko.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 Merkko.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.
merkko.com
Open Graph description is not detected on the main page of Merkko. 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: