18.1 sec in total
2.5 sec
14.2 sec
1.3 sec
Welcome to rhazesglobal.com homepage info - get ready to check Rhazes Global best content right away, or after learning these important things about rhazesglobal.com
Search the best hospitals and doctors from our online platform. Analyze positive impression on our patients after their treatments.
Visit rhazesglobal.comWe analyzed Rhazesglobal.com page load time and found that the first response time was 2.5 sec and then it took 15.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rhazesglobal.com performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value32.0 s
0/100
25%
Value16.2 s
0/100
10%
Value6,430 ms
0/100
30%
Value0
100/100
15%
Value23.2 s
1/100
10%
2492 ms
69 ms
123 ms
660 ms
768 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 50% of them (52 requests) were addressed to the original Rhazesglobal.com, 13% (13 requests) were made to Fonts.gstatic.com and 9% (9 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (9.3 sec) belongs to the original domain Rhazesglobal.com.
Page size can be reduced by 1.5 MB (20%)
7.3 MB
5.8 MB
In fact, the total size of Rhazesglobal.com main page is 7.3 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.0 MB which makes up the majority of the site volume.
Potential reduce by 1.0 MB
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 239.0 kB, which is 20% 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 1.0 MB or 86% of the original size.
Potential reduce by 471.4 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. Rhazes Global images are well optimized though.
Potential reduce by 5.6 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 128 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. Rhazesglobal.com has all CSS files already compressed.
Number of requests can be reduced by 30 (36%)
84
54
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rhazes Global. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and as a result speed up the page load time.
rhazesglobal.com
2492 ms
gtm.js
69 ms
js
123 ms
app.bundle.min.css
660 ms
app-top.bundle.min.js
768 ms
analytics.js
118 ms
hotjar-2861769.js
274 ms
js
51 ms
js
157 ms
email-decode.min.js
57 ms
api.js
270 ms
app.bundle.min.js
1034 ms
GetAll
688 ms
GetScripts
831 ms
common.bundle.min.js
591 ms
_Header.min.js
1016 ms
tp.widget.bootstrap.min.js
247 ms
Index.min.js
1017 ms
collect
116 ms
collect
160 ms
collect
132 ms
conversion_async.js
90 ms
modules.cbd9768ba80ba0be5b17.js
77 ms
138 ms
103 ms
265 ms
23 ms
logo2.png
4730 ms
bc87f98c-583e-4ab5-8c78-74845b4a5722.jpg
4738 ms
cc13c44d-915b-465d-86c7-a47f606964c5.jpg
4736 ms
ec8572ef-f286-4014-8048-e00402943af6.jpg
4741 ms
3213f6c1-6bff-47fc-8d99-9fb1b33ed1f5.jpeg
4741 ms
e9d44bf8-6ee0-48e2-bf09-290dcc36b62a.png
5472 ms
dce47839-b054-4e3b-981e-0de3a0a3d815.jpeg
5713 ms
9a044eea-f714-4947-bc16-f350bf983556.png
6222 ms
112cc56c-4250-46cf-b891-ac7004c81683.jpg
5712 ms
799eae1f-8a71-420d-8cdc-b5cde91c4579.jpg
5711 ms
0aff427b-200c-4409-aded-eb523a55081c.jpg
5711 ms
680fdafb-643c-4ef4-87c9-719b2b3774e9.jpg
6216 ms
f8e3527b-0676-4630-90be-b09290d2723f.jpg
6339 ms
6cd86b30-95b4-4fe4-80c0-74b3eec2b0fa.jpg
6362 ms
8c2c1bdf-5ce7-4e1e-b0ac-f73325a17b99.jpg
6346 ms
46fc498c-0004-4640-93aa-3edc6233a294.jpg
6216 ms
09ae7785-3210-4054-b845-de330ac62a62.jpg
7001 ms
ea6e0daa-75c0-468d-bf82-638e6fb10528.jpg
6993 ms
f8a00d4c-3d1c-4c72-b6ac-94f4d670fa2f.jpg
6999 ms
0e4aacb4-c2b5-4c9d-ad40-9b0bf3d19a79.png
7002 ms
GetProfilePictureById
6641 ms
b8c52826-5edf-4c5e-98e6-b12ea60cd17d.png
7252 ms
24e4608b-11e9-4653-a56d-8867113fd04b.png
8866 ms
939d8290-8ced-476b-b216-47b121b8c8de.png
8890 ms
e6716d91-dcba-4453-ac7c-e9f42b1fa4fe.png
8893 ms
ae2e2e24-c5f0-4045-99e3-deb332ad1024.png
8883 ms
b4f5b635-66c2-477f-acb6-573e770ee0b9.png
8880 ms
3919d51a-d04a-49a4-9127-f4202b894251.png
8881 ms
8d634bb2-4450-4e07-8d9e-bdac2ca4b415.png
8881 ms
e5d861b6-4996-4548-880f-79ed832cf161.png
8984 ms
aeff2e27-64a0-4beb-9cd7-2a215a9623a3.png
9325 ms
6bcf2d0c-a0c9-4fc8-a5fd-de5b0d49ee9f.png
9098 ms
4b36c789-20c4-4287-be75-4d541dddd444.png
9090 ms
XRXW3I6Li01BKofA6sKkZg.ttf
4576 ms
XRXW3I6Li01BKofAjsOkZg.ttf
4589 ms
XRXW3I6Li01BKofAksCkZg.ttf
5699 ms
XRXW3I6Li01BKofAtsGkZg.ttf
5542 ms
XRXV3I6Li01BKof4Mg.ttf
5699 ms
fa-solid-900.woff
9276 ms
JTURjIg1_i6t8kCHKm45_dJE7g4.ttf
4429 ms
JTURjIg1_i6t8kCHKm45_c5H7g4.ttf
5128 ms
JTURjIg1_i6t8kCHKm45_epG7g4.ttf
5362 ms
JTURjIg1_i6t8kCHKm45_bZF7g4.ttf
5520 ms
JTURjIg1_i6t8kCHKm45_ZpC7g4.ttf
5869 ms
JTUSjIg1_i6t8kCHKm45xW4.ttf
5874 ms
fa-regular-400.woff
9188 ms
recaptcha__en.js
5813 ms
default
5621 ms
init.js
6007 ms
json
4601 ms
fa-light-300.woff
5743 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
1785 ms
fa-brands-400.woff
5105 ms
flags.png
5103 ms
city7.png
5176 ms
famfamfam-flags.png
5377 ms
4.jpg
5394 ms
bg.jpg
4814 ms
fallback
116 ms
fallback
308 ms
fallback__ltr.css
205 ms
css
1662 ms
visit-data
1986 ms
logo_48.png
18 ms
KFOmCnqEu92Fr1Mu4mxM.woff
4 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
6 ms
content
1350 ms
utils.js
57 ms
twk-event-polyfill.js
186 ms
twk-entries-polyfill.js
86 ms
twk-main.js
107 ms
twk-vendor.js
139 ms
twk-chunk-vendors.js
206 ms
twk-chunk-common.js
173 ms
twk-runtime.js
147 ms
twk-app.js
165 ms
rhazesglobal.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
rhazesglobal.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
rhazesglobal.com 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rhazesglobal.com 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 Rhazesglobal.com 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.
rhazesglobal.com
Open Graph description is not detected on the main page of Rhazes Global. 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: