Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

mergely.com

Mergely - Compare and merge document differences online

Page Load Speed

1.9 sec in total

First Response

422 ms

Resources Loaded

1.3 sec

Page Rendered

142 ms

mergely.com screenshot

About Website

Welcome to mergely.com homepage info - get ready to check Mergely best content for India right away, or after learning these important things about mergely.com

Mergely is a javascript library that allows you to diff online, and integrate with your CMS

Visit mergely.com

Key Findings

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

Performance Metrics

mergely.com performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

54/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

mergely.com

422 ms

css

27 ms

berlin-sans-fb-demi.css

180 ms

mergely.css

270 ms

mergely.css

275 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 67% of them (12 requests) were addressed to the original Mergely.com, 11% (2 requests) were made to Google-analytics.com and 11% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (644 ms) belongs to the original domain Mergely.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.0 kB (20%)

Content Size

160.7 kB

After Optimization

128.8 kB

In fact, the total size of Mergely.com main page is 160.7 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. 15% of websites need less resources to load. Images take 131.2 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 3.3 kB

  • Original 5.0 kB
  • After minification 4.0 kB
  • After compression 1.6 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 1.0 kB, which is 20% 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 3.3 kB or 67% of the original size.

Image Optimization

-18%

Potential reduce by 23.3 kB

  • Original 131.2 kB
  • After minification 107.9 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. Obviously, Mergely needs image optimization as it can save up to 23.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-72%

Potential reduce by 5.3 kB

  • Original 7.4 kB
  • After minification 6.6 kB
  • After compression 2.1 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. Mergely.com needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (20%)

Requests Now

15

After Optimization

12

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

Accessibility Review

mergely.com accessibility score

95

Accessibility Issues

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.

Best Practices

mergely.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mergely.com SEO score

75

Search Engine Optimization Advices

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 Mergely.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 Mergely.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.

Social Sharing Optimization

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