Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

watermark.ws

Watermark Photos And Videos Online - Add Custom Watermarks

Page Load Speed

1.5 sec in total

First Response

72 ms

Resources Loaded

597 ms

Page Rendered

829 ms

watermark.ws screenshot

About Website

Click here to check amazing Watermark content for Mexico. Otherwise, check out these important facts you probably never knew about watermark.ws

Protect your photos with custom watermarks. Save watermarks as templates for later use. Watermark animated GIFs, preserving all layers of animation. Batch process and watermark many files at once.

Visit watermark.ws

Key Findings

We analyzed Watermark.ws page load time and found that the first response time was 72 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 30% of websites can load faster.

Performance Metrics

watermark.ws performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value640 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

watermark.ws

72 ms

watermark.ws

44 ms

app.css

6 ms

analytics.min.js

445 ms

bg-landscape.svg

3 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 91% of them (10 requests) were addressed to the original Watermark.ws, 9% (1 request) were made to Cdn.segment.com. The less responsive or slowest element that took the longest time to load (445 ms) relates to the external source Cdn.segment.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 42.7 kB (44%)

Content Size

97.0 kB

After Optimization

54.3 kB

In fact, the total size of Watermark.ws main page is 97.0 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. 40% of websites need less resources to load. HTML takes 58.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 42.7 kB

  • Original 58.6 kB
  • After minification 55.3 kB
  • After compression 15.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 42.7 kB or 73% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 38.4 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.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Watermark. According to our analytics all requests are already optimized.

Accessibility Review

watermark.ws accessibility score

64

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

watermark.ws best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

watermark.ws SEO score

99

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 Watermark.ws 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 Watermark.ws 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 Watermark. 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: