Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 69

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

merchantwords.com

MerchantWords | The Largest Database of Shopper Search Trends

Page Load Speed

1.3 sec in total

First Response

228 ms

Resources Loaded

768 ms

Page Rendered

263 ms

merchantwords.com screenshot

About Website

Welcome to merchantwords.com homepage info - get ready to check Merchant Words best content for United States right away, or after learning these important things about merchantwords.com

Uncover product opportunities, spy on your competition, create successful marketing campaigns, and grow your sales and business with our tools and services.

Visit merchantwords.com

Key Findings

We analyzed Merchantwords.com page load time and found that the first response time was 228 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

merchantwords.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value17.3 s

0/100

10%

TBT (Total Blocking Time)

Value6,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value25.9 s

1/100

10%

Network Requests Diagram

www.merchantwords.com

228 ms

bootstrap.css

14 ms

bootstrap-responsive.css

32 ms

theme.css

33 ms

animate.css

38 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 45% of them (20 requests) were addressed to the original Merchantwords.com, 18% (8 requests) were made to Fonts.gstatic.com and 14% (6 requests) were made to Assets.zendesk.com. The less responsive or slowest element that took the longest time to load (344 ms) relates to the external source Jz206.infusionsoft.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 341.5 kB (49%)

Content Size

702.9 kB

After Optimization

361.4 kB

In fact, the total size of Merchantwords.com main page is 702.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. CSS take 261.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 15.7 kB

  • Original 20.9 kB
  • After minification 14.8 kB
  • After compression 5.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 6.1 kB, which is 29% 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 15.7 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 7.2 kB

  • Original 225.2 kB
  • After minification 218.0 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. Merchant Words images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 92.4 kB

  • Original 195.3 kB
  • After minification 190.8 kB
  • After compression 102.9 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 92.4 kB or 47% of the original size.

CSS Optimization

-86%

Potential reduce by 226.1 kB

  • Original 261.5 kB
  • After minification 211.8 kB
  • After compression 35.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. Merchantwords.com needs all CSS files to be minified and compressed as it can save up to 226.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (38%)

Requests Now

34

After Optimization

21

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Merchant Words. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

merchantwords.com accessibility score

80

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

merchantwords.com best practices score

69

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Uses deprecated APIs

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

merchantwords.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Merchantwords.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 Merchantwords.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Merchant Words. 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: