1.2 sec in total
380 ms
754 ms
65 ms
Click here to check amazing Watch content. Otherwise, check out these important facts you probably never knew about watch.li
Visit watch.liWe analyzed Watch.li page load time and found that the first response time was 380 ms and then it took 819 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
watch.li performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value9.6 s
0/100
25%
Value7.6 s
25/100
10%
Value3,580 ms
1/100
30%
Value0
100/100
15%
Value16.6 s
5/100
10%
380 ms
327 ms
37 ms
Our browser made a total of 3 requests to load all elements on the main page. We found that 33% of them (1 request) were addressed to the original Watch.li, 33% (1 request) were made to Sedo.com and 33% (1 request) were made to Cdn.sedo.com. The less responsive or slowest element that took the longest time to load (380 ms) belongs to the original domain Watch.li.
Page size can be reduced by 2.1 kB (11%)
18.9 kB
16.7 kB
In fact, the total size of Watch.li main page is 18.9 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 16.4 kB which makes up the majority of the site volume.
Potential reduce by 1.3 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 1.3 kB or 52% of the original size.
Potential reduce by 871 B
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. Watch.li has all CSS files already compressed.
We found no issues to fix!
1
1
The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Watch. According to our analytics all requests are already optimized.
watch.li
380 ms
327 ms
index.css
37 ms
watch.li accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
watch.li best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
watch.li SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watch.li 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 Watch.li 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.
watch.li
Open Graph description is not detected on the main page of Watch. 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: