Tools & Wizards About Us
merge1.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

merge1.com

Merge1: Data collection for all your communications in one place | Veritas

Page Load Speed

4 sec in total

First Response

1.5 sec

Resources Loaded

2.5 sec

Page Rendered

56 ms

merge1.com screenshot

About Website

Welcome to merge1.com homepage info - get ready to check Merge1 best content right away, or after learning these important things about merge1.com

Merge1 can simplify all your eDiscovery and Compliance needs by ensuring data collection from all sources in one place.

Visit merge1.com

Key Findings

We analyzed Merge1.com page load time and found that the first response time was 1.5 sec and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

merge1.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value11,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value39.2 s

0/100

10%

Network Requests Diagram

merge1

1476 ms

gtm.js

52 ms

clientlib-base.min.3b475a6292b07699b36759510e115420.css

157 ms

clientlib-dependencies.min.32b13ffe3035b56c2b6cff8b342e4ced.js

132 ms

clientlib-dependencies.min.a5d27bab57acd9aa77671a1db4d36a39.css

333 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Merge1.com, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Veritas.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 733.4 kB (24%)

Content Size

3.1 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Merge1.com main page is 3.1 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 194.8 kB

  • Original 226.5 kB
  • After minification 134.5 kB
  • After compression 31.7 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 92.1 kB, which is 41% 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 194.8 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 226.8 kB

  • Original 2.4 MB
  • After minification 2.2 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. Merge1 images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 311.8 kB

  • Original 433.3 kB
  • After minification 433.3 kB
  • After compression 121.6 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 311.8 kB or 72% of the original size.

Requests Breakdown

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

Requests Now

46

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

merge1

merge1

1476 ms

gtm.js

gtm.js

52 ms

clientlib-base.min.3b475a6292b07699b36759510e115420.css

clientlib-base.min.3b475a6292b07699b36759510e115420.css

157 ms

clientlib-dependencies.min.32b13ffe3035b56c2b6cff8b342e4ced.js

clientlib-dependencies.min.32b13ffe3035b56c2b6cff8b342e4ced.js

132 ms

clientlib-dependencies.min.a5d27bab57acd9aa77671a1db4d36a39.css

clientlib-dependencies.min.a5d27bab57acd9aa77671a1db4d36a39.css

333 ms

clientlib-site.min.0e55b664dce88c3f333b235ee8f8535d.css

clientlib-site.min.0e55b664dce88c3f333b235ee8f8535d.css

313 ms

launch-26e4d838c6cd.min.js

launch-26e4d838c6cd.min.js

21 ms

clientlib-site.min.f142abe9ee3b2cba8155b2a766fcabc4.js

clientlib-site.min.f142abe9ee3b2cba8155b2a766fcabc4.js

180 ms

container.min.64e934d0a16266574945c8fb92e68316.js

container.min.64e934d0a16266574945c8fb92e68316.js

140 ms

clientlib-base.min.435c38bcca0334acb099a80756c64334.js

clientlib-base.min.435c38bcca0334acb099a80756c64334.js

135 ms

DBJ88-GSVDU-M2DSD-VRUXA-63SUJ

DBJ88-GSVDU-M2DSD-VRUXA-63SUJ

62 ms

Alta_RGB_standard-image.png

Alta_RGB_standard-image.png

57 ms

img.png

img.png

57 ms

img.png

img.png

119 ms

img.png

img.png

116 ms

merge1-microsoft-teams.png

merge1-microsoft-teams.png

67 ms

merge1-content-sources.png

merge1-content-sources.png

68 ms

merge1-globe-750.png

merge1-globe-750.png

67 ms

slack.png

slack.png

117 ms

zoom-meetings.png

zoom-meetings.png

116 ms

webex-teams.png

webex-teams.png

116 ms

salesforce.png

salesforce.png

119 ms

microsoft-teams.png

microsoft-teams.png

147 ms

bloomberg.png

bloomberg.png

117 ms

symphony.png

symphony.png

118 ms

ringcentral.png

ringcentral.png

118 ms

whats-app.png

whats-app.png

148 ms

aws-logo.png

aws-logo.png

119 ms

Merge1_product-icons-white-bkg1.png

Merge1_product-icons-white-bkg1.png

125 ms

img.png

img.png

126 ms

img.png

img.png

129 ms

img.png

img.png

136 ms

img.png

img.png

143 ms

datainsights-product-icons-white-bkg.png

datainsights-product-icons-white-bkg.png

144 ms

enterprise-vault-product-icons-white-bkg.png

enterprise-vault-product-icons-white-bkg.png

156 ms

alta-archiving-white.png

alta-archiving-white.png

160 ms

img.png

img.png

162 ms

img.png

img.png

207 ms

img.png

img.png

165 ms

img.png

img.png

173 ms

vtas.png

vtas.png

180 ms

img.jpg

img.jpg

314 ms

image-top-diamonds.svg

image-top-diamonds.svg

300 ms

img.jpg

img.jpg

289 ms

img.jpg

img.jpg

442 ms

img.png

img.png

197 ms

GalaxiePolaris-Book.woff

GalaxiePolaris-Book.woff

203 ms

GalaxiePolaris-Medium.woff

GalaxiePolaris-Medium.woff

228 ms

GalaxiePolaris-Bold.woff

GalaxiePolaris-Bold.woff

251 ms

config.json

config.json

44 ms

Accessibility Review

merge1.com accessibility score

69

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-*] attributes do not match their roles

High

ARIA IDs are not unique

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

Best Practices

merge1.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

merge1.com SEO score

71

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

High

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

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

merge1.com

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