1.4 sec in total
286 ms
1 sec
96 ms
Visit redis.io now to see the best up-to-date Redis content for China and also check out these interesting facts you probably never knew about redis.io
Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures …
Visit redis.ioWe analyzed Redis.io page load time and found that the first response time was 286 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
redis.io performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value6.1 s
12/100
25%
Value4.4 s
73/100
10%
Value180 ms
92/100
30%
Value0.082
94/100
15%
Value6.1 s
63/100
10%
286 ms
362 ms
150 ms
21 ms
257 ms
Our browser made a total of 16 requests to load all elements on the main page. We found that 44% of them (7 requests) were addressed to the original Redis.io, 19% (3 requests) were made to Fonts.gstatic.com and 13% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (362 ms) belongs to the original domain Redis.io.
Page size can be reduced by 78.6 kB (42%)
187.4 kB
108.8 kB
In fact, the total size of Redis.io main page is 187.4 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. 20% of websites need less resources to load. Javascripts take 77.1 kB which makes up the majority of the site volume.
Potential reduce by 4.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. This page needs HTML code to be minified as it can gain 1.3 kB, which is 17% 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 4.9 kB or 67% of the original size.
Potential reduce by 8.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, Redis needs image optimization as it can save up to 8.9 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 11.7 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 11.7 kB or 15% of the original size.
Potential reduce by 53.0 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. Redis.io needs all CSS files to be minified and compressed as it can save up to 53.0 kB or 78% of the original size.
We found no issues to fix!
11
11
The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Redis. According to our analytics all requests are already optimized.
redis.io
286 ms
redis.io
362 ms
styles.css
150 ms
jquery.min.js
21 ms
app.js
257 ms
css
30 ms
font-awesome.min.css
22 ms
ga.js
23 ms
redis-white.png
152 ms
redis-small.png
106 ms
redislabs.png
178 ms
__utm.gif
13 ms
redis-buzz.herokuapp.com
112 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
28 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
32 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
34 ms
redis.io 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.
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
Links do not have a discernible name
redis.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
redis.io SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Redis.io 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 Redis.io 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.
redis.io
Open Graph description is not detected on the main page of Redis. 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: