Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

merchantspring.io

MerchantSpring | Marketplace Analytics and Reporting for Agencies and Brands

Page Load Speed

3 sec in total

First Response

187 ms

Resources Loaded

1.6 sec

Page Rendered

1.2 sec

merchantspring.io screenshot

About Website

Visit merchantspring.io now to see the best up-to-date Merchant Spring content for Australia and also check out these interesting facts you probably never knew about merchantspring.io

Unified performance analytics across 120+ eCommerce and retail media channels — from Amazon and Walmart to TikTok and Meta — all through secure, authorized data connections.

Visit merchantspring.io

Key Findings

We analyzed Merchantspring.io page load time and found that the first response time was 187 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

merchantspring.io performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value8,340 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value26.1 s

0/100

10%

Network Requests Diagram

merchantspring.io

187 ms

slick-theme.css

71 ms

slick.min.css

78 ms

jquery.min.js

67 ms

slick.min.js

76 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 72% of them (68 requests) were addressed to the original Merchantspring.io, 6% (6 requests) were made to Cdnjs.cloudflare.com and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (911 ms) belongs to the original domain Merchantspring.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.0 kB (10%)

Content Size

1.3 MB

After Optimization

1.2 MB

In fact, the total size of Merchantspring.io main page is 1.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 108.7 kB

  • Original 124.8 kB
  • After minification 109.5 kB
  • After compression 16.1 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 15.4 kB, which is 12% 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 108.7 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 13.2 kB

  • Original 1.1 MB
  • After minification 1.1 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. Merchant Spring images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 7.3 kB

  • Original 93.0 kB
  • After minification 93.0 kB
  • After compression 85.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. This website has mostly compressed JavaScripts.

CSS Optimization

-12%

Potential reduce by 1.8 kB

  • Original 15.8 kB
  • After minification 15.8 kB
  • After compression 13.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. Merchantspring.io needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (41%)

Requests Now

83

After Optimization

49

The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Merchant Spring. 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.

Accessibility Review

merchantspring.io accessibility score

92

Accessibility Issues

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

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

merchantspring.io best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

merchantspring.io SEO score

97

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Merchantspring.io 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 Merchantspring.io 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.

Social Sharing Optimization

Open Graph data is detected on the main page of Merchant Spring. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: