14.2 sec in total
2.7 sec
11.1 sec
387 ms
Visit rayzz.net now to see the best up-to-date Rayzz content for India and also check out these interesting facts you probably never knew about rayzz.net
Search our knowledge base for drug interactions, pharmacology, chemical structures, targets, metabolism, & more. Download limited datasets, free for
Visit rayzz.netWe analyzed Rayzz.net page load time and found that the first response time was 2.7 sec and then it took 11.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rayzz.net performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value9.7 s
0/100
25%
Value16.3 s
0/100
10%
Value150 ms
94/100
30%
Value0
100/100
15%
Value9.0 s
34/100
10%
2668 ms
83 ms
166 ms
353 ms
248 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 93% of them (40 requests) were addressed to the original Rayzz.net, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Stats.wpmucdn.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Rayzz.net.
Page size can be reduced by 82.6 kB (11%)
719.1 kB
636.5 kB
In fact, the total size of Rayzz.net main page is 719.1 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. 25% of websites need less resources to load. Images take 432.4 kB which makes up the majority of the site volume.
Potential reduce by 54.2 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 54.2 kB or 80% of the original size.
Potential reduce by 18.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. Rayzz images are well optimized though.
Potential reduce by 2.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 6.7 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. Rayzz.net has all CSS files already compressed.
Number of requests can be reduced by 26 (65%)
40
14
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rayzz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
rayzz.net
2668 ms
styles.css
83 ms
09b5a337087f645153f364a3aca1761a.css
166 ms
bootstrap.css
353 ms
fontawesome-all.css
248 ms
style.css
249 ms
responsive.css
257 ms
elementor-icons.min.css
256 ms
frontend-lite.min.css
272 ms
swiper.min.css
345 ms
post-5.css
1635 ms
all.min.css
363 ms
v4-shims.min.css
361 ms
post-8.css
1736 ms
css
31 ms
jquery.min.js
513 ms
jquery-migrate.min.js
432 ms
v4-shims.min.js
446 ms
index.js
447 ms
index.js
512 ms
navigation.js
524 ms
script.js
527 ms
webpack.runtime.min.js
591 ms
frontend-modules.min.js
594 ms
waypoints.min.js
602 ms
core.min.js
607 ms
frontend.min.js
672 ms
underscore.min.js
674 ms
wp-util.min.js
679 ms
frontend.min.js
687 ms
blue.png
86 ms
cropped-700.jpg
322 ms
Articles_Blue-f956f886-300x230.png
86 ms
145_main.jpg
238 ms
3333333333333333.jpg
322 ms
t1.jpg
244 ms
800.png
390 ms
qz1.jpg
320 ms
Untitled-design-83.jpg
322 ms
20000-1.gif
866 ms
Buy-Viagra-Australia-b-500x500-1.jpg
404 ms
analytics.js
47 ms
157 ms
rayzz.net accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
rayzz.net 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
Detected JavaScript libraries
Browser errors were logged to the console
rayzz.net SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rayzz.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Rayzz.net 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.
rayzz.net
Open Graph data is detected on the main page of Rayzz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: