2.9 sec in total
321 ms
2.2 sec
366 ms
Welcome to rajahospital.com homepage info - get ready to check Raja Hospital best content right away, or after learning these important things about rajahospital.com
Welcome to Raja Hospital, Nawanshahr's Best Healthcare Support with Affordable Excellence, Including IVF and Trauma & Accidental Treatment Centre.
Visit rajahospital.comWe analyzed Rajahospital.com page load time and found that the first response time was 321 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
rajahospital.com performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value8.1 s
2/100
25%
Value11.1 s
6/100
10%
Value890 ms
32/100
30%
Value1.706
0/100
15%
Value14.1 s
9/100
10%
321 ms
35 ms
58 ms
95 ms
189 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 70% of them (83 requests) were addressed to the original Rajahospital.com, 9% (11 requests) were made to Maps.googleapis.com and 8% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Rajahospital.com.
Page size can be reduced by 1.4 MB (43%)
3.2 MB
1.8 MB
In fact, the total size of Rajahospital.com main page is 3.2 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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 85.4 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 85.4 kB or 90% of the original size.
Potential reduce by 33.8 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. Raja Hospital images are well optimized though.
Potential reduce by 880.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 880.9 kB or 69% of the original size.
Potential reduce by 369.4 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. Rajahospital.com needs all CSS files to be minified and compressed as it can save up to 369.4 kB or 85% of the original size.
Number of requests can be reduced by 39 (37%)
106
67
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Raja Hospital. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
rajahospital.com
321 ms
css
35 ms
css
58 ms
jquery-ui-1.10.3.custom.css
95 ms
animate.css
189 ms
font-awesome.min.css
186 ms
blue.css
386 ms
settings.min.css
193 ms
slides.css
181 ms
inline.min.css
181 ms
lightbox.css
271 ms
embed
184 ms
jquery.min.js
473 ms
jquery-ui-1.10.3.custom.min.js
470 ms
bootstrap.min.js
269 ms
lightbox.js
270 ms
jquery.themepunch.tools.min.js
469 ms
jquery.themepunch.revolution.min.js
468 ms
jquery.scrollUp.min.js
357 ms
jquery.sticky.min.js
467 ms
wow.min.js
468 ms
jquery.flexisel.min.js
543 ms
jquery.med.min.js
648 ms
custom.min.js
544 ms
loader.gif
646 ms
rlogo.png
549 ms
logos.png
819 ms
slide-4.jpg
892 ms
slide-1.jpg
818 ms
s1-img3.png
644 ms
slide-2.jpg
899 ms
s2-img2.png
803 ms
s3-ic1.png
804 ms
s3-ic2.png
888 ms
s3-ic3.png
889 ms
s3-ic4.png
896 ms
s3-ic5.png
896 ms
s3-ic6.png
1048 ms
s3-ic7.png
1048 ms
s3-ic8.png
1047 ms
s3-ic9.png
976 ms
s3-ic10.png
888 ms
s3-ic11.png
886 ms
s3-ic12.png
975 ms
js
42 ms
init_embed.js
30 ms
s3-ic13.png
967 ms
s3-ic14.png
966 ms
s3-ic15.png
888 ms
s3-ic16.png
881 ms
slide-3.jpg
973 ms
abt.jpg
994 ms
share_addon.js
71 ms
facs.jpg
974 ms
doc-1.jpg
787 ms
doc-2.jpg
775 ms
doc-3.jpg
777 ms
pic07.jpg
859 ms
LeFlHvsZjXu2c3ZRgBq9nKCWcynf_cDxXwCLxiixG1c.ttf
47 ms
PIbvSEyHEdL91QLOQRnZ14nF5uFdDttMLvmWuJdhhgs.ttf
48 ms
icomoon.woff
860 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
47 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
48 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
47 ms
fontawesome-webfont.woff
906 ms
pic24.jpg
804 ms
pic4.jpg
873 ms
pic18.jpg
867 ms
common.js
30 ms
map.js
29 ms
google4.png
169 ms
overlay.js
9 ms
util.js
134 ms
onion.js
165 ms
search_impl.js
166 ms
StaticMapService.GetMapImage
211 ms
pic20.jpg
792 ms
pic31.jpg
792 ms
ricf.jpg
736 ms
ViewportInfoService.GetViewportInfo
30 ms
kh
99 ms
transparent.png
16 ms
nabh.png
697 ms
qa.png
703 ms
echf.png
701 ms
hi.png
699 ms
vt
214 ms
controls.js
13 ms
vt
206 ms
vt
207 ms
vt
206 ms
vt
193 ms
css
58 ms
mapcnt6.png
28 ms
sv9.png
25 ms
bsnl.png
634 ms
phm.png
698 ms
ba.png
698 ms
uhc.png
694 ms
hsp-bg.jpg
802 ms
ov-plus.png
707 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
112 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
112 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
119 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
119 ms
doc.png
733 ms
list-arrow-foot.png
625 ms
close.png
629 ms
loading.gif
630 ms
prev.png
640 ms
next.png
731 ms
AuthenticationService.Authenticate
17 ms
left-car-gen.jpg
641 ms
right-car-gen.jpg
640 ms
up-scroll.png
641 ms
loader.gif
644 ms
timer.png
728 ms
large_left.png
637 ms
large_right.png
636 ms
rajahospital.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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
rajahospital.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
rajahospital.com 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
Image elements do not have [alt] attributes
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 Rajahospital.com 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 Rajahospital.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.
rajahospital.com
Open Graph description is not detected on the main page of Raja Hospital. 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: