776 ms in total
12 ms
554 ms
210 ms
Visit screener.co now to see the best up-to-date Screener content for India and also check out these interesting facts you probably never knew about screener.co
Screener.co is the most powerful global stock screening tool for individual investors.
Visit screener.coWe analyzed Screener.co page load time and found that the first response time was 12 ms and then it took 764 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.
screener.co performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value10.1 s
0/100
25%
Value7.6 s
26/100
10%
Value170 ms
92/100
30%
Value0.091
92/100
15%
Value10.2 s
25/100
10%
12 ms
104 ms
12 ms
43 ms
28 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 84% of them (61 requests) were addressed to the original Screener.co, 3% (2 requests) were made to Redditstatic.com and 3% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (347 ms) relates to the external source App.getreditus.com.
Page size can be reduced by 530.8 kB (31%)
1.7 MB
1.2 MB
In fact, the total size of Screener.co main page is 1.7 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. 60% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 26.0 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 8.3 kB, which is 25% 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 26.0 kB or 77% of the original size.
Potential reduce by 9.2 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. Screener images are well optimized though.
Potential reduce by 387.0 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 387.0 kB or 69% of the original size.
Potential reduce by 108.5 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. Screener.co needs all CSS files to be minified and compressed as it can save up to 108.5 kB or 86% of the original size.
Number of requests can be reduced by 37 (53%)
70
33
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Screener. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
{{url}}
{{time}} ms
screener.co accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
screener.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
screener.co SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Screener.co 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 Screener.co 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.
{{og_description}}
screener.co
Open Graph description is not detected on the main page of Screener. 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: