12.8 sec in total
1.5 sec
10 sec
1.3 sec
Welcome to hamshospital.com homepage info - get ready to check HAMS Hospital best content for Nepal right away, or after learning these important things about hamshospital.com
Visit hamshospital.comWe analyzed Hamshospital.com page load time and found that the first response time was 1.5 sec and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
hamshospital.com performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value17.0 s
0/100
25%
Value17.8 s
0/100
10%
Value3,810 ms
1/100
30%
Value0.443
21/100
15%
Value39.1 s
0/100
10%
1470 ms
36 ms
1044 ms
548 ms
546 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 86% of them (139 requests) were addressed to the original Hamshospital.com, 9% (15 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Hamshospital.com.
Page size can be reduced by 1.9 MB (20%)
9.6 MB
7.6 MB
In fact, the total size of Hamshospital.com main page is 9.6 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 7.3 MB which makes up the majority of the site volume.
Potential reduce by 254.8 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 103.1 kB, which is 37% 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 254.8 kB or 92% of the original size.
Potential reduce by 269.6 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. HAMS Hospital images are well optimized though.
Potential reduce by 735.5 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 735.5 kB or 59% of the original size.
Potential reduce by 681.3 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. Hamshospital.com needs all CSS files to be minified and compressed as it can save up to 681.3 kB or 90% of the original size.
Number of requests can be reduced by 52 (37%)
142
90
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HAMS 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 33 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
hamshospital.com
1470 ms
css2
36 ms
style.min.css
1044 ms
styles.css
548 ms
ivory-search.min.css
546 ms
style.css
815 ms
bootstrap.min.css
1585 ms
animate.css
1096 ms
font-awesome.css
1080 ms
flaticon.css
815 ms
themify-icons.css
1085 ms
slick.css
1087 ms
prettyPhoto.css
1306 ms
shortcodes.css
1880 ms
main.css
1622 ms
megamenu.css
1354 ms
responsive.css
1367 ms
rs6.css
1568 ms
magnific-popup.css
1627 ms
override5.css
1642 ms
jquery.min.js
2093 ms
jquery-migrate.min.js
1846 ms
sdk.js
26 ms
index.js
1639 ms
index.js
1640 ms
jquery.min.js
2112 ms
jquery-migrate-1.4.1.min.js
2107 ms
tether.min.js
2109 ms
bootstrap.min.js
2111 ms
jquery.easing.js
2110 ms
jquery-waypoints.js
2112 ms
jquery-validate.js
2150 ms
slick.min.js
2256 ms
imagesloaded.min.js
2255 ms
jquery-isotope.js
2255 ms
jquery.prettyPhoto.js
2266 ms
numinate.min.js
2442 ms
circle-progress.min.js
2442 ms
api.js
93 ms
main.js
2477 ms
magnific-popup.min.js
2750 ms
slider.js
2187 ms
revolution.tools.min.js
2502 ms
rs6.min.js
2544 ms
override.js
2263 ms
navigation.js
2231 ms
wp-polyfill-inert.min.js
2228 ms
regenerator-runtime.min.js
2228 ms
wp-polyfill.min.js
2611 ms
index.js
2053 ms
ivory-search.min.js
2005 ms
css2
24 ms
css2
25 ms
hams-hospital-logo-1.png
1144 ms
news.svg
1269 ms
ambulance.png
1270 ms
helicopter.png
1328 ms
Asset-4.png
1328 ms
Asset-1.png
1329 ms
Asset-36.png
1406 ms
Asset-2.png
1463 ms
Asset-3.png
1720 ms
Asset-5.png
1720 ms
Asset-6.png
1579 ms
Asset-7.png
1578 ms
Asset-8.png
1675 ms
Asset-10.png
1676 ms
Asset-11.png
1711 ms
Asset-12.png
1716 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
181 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf
180 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
138 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
181 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
181 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
179 ms
fontawesome-webfont3e6e.woff
1696 ms
92zPtBhPNqw79Ij1E865zBUv7myRJQVG.ttf
182 ms
92zPtBhPNqw79Ij1E865zBUv7myjJQVG.ttf
186 ms
92zPtBhPNqw79Ij1E865zBUv7mz9JQVG.ttf
184 ms
92zPtBhPNqw79Ij1E865zBUv7mwjJQVG.ttf
185 ms
92zPtBhPNqw79Ij1E865zBUv7myjJAVG.ttf
181 ms
92zPtBhPNqw79Ij1E865zBUv7mx9IgVG.ttf
184 ms
92zPtBhPNqw79Ij1E865zBUv7mxEIgVG.ttf
187 ms
92zPtBhPNqw79Ij1E865zBUv7mwjIgVG.ttf
186 ms
92zPtBhPNqw79Ij1E865zBUv7mwKIgVG.ttf
186 ms
sdk.js
53 ms
themify9f24.woff
1737 ms
Asset-13.png
1778 ms
Asset-14.png
1772 ms
Asset-15.png
1825 ms
Asset-16.png
1830 ms
Asset-17.png
1667 ms
Asset-18.png
1732 ms
Asset-19.png
1738 ms
Asset-20.png
1174 ms
Asset-21.png
1303 ms
Asset-22.png
1310 ms
Asset-23.png
1324 ms
Asset-25.png
1395 ms
Asset-26.png
1378 ms
Asset-27.png
1388 ms
Asset-28.png
1523 ms
Asset-29.png
1530 ms
Asset-30.png
1544 ms
Asset-31.png
1559 ms
Asset-32.png
1511 ms
Asset-33.png
1464 ms
Asset-34.png
1606 ms
Asset-35.png
1613 ms
proccess-box-arrow.png
1612 ms
recaptcha__en.js
42 ms
doctor.png
1628 ms
library.png
1554 ms
career.png
1332 ms
package.png
1481 ms
Website-banner-1-01-02-02-01.png
2295 ms
Website-banner-1-01-02-02-02.png
2045 ms
timthumb.php
1491 ms
timthumb.php
1749 ms
timthumb.php
1481 ms
timthumb.php
1883 ms
timthumb.php
1724 ms
140 ms
timthumb.php
1645 ms
timthumb.php
1811 ms
timthumb.php
1781 ms
timthumb.php
1791 ms
timthumb.php
2160 ms
timthumb.php
1918 ms
timthumb.php
1971 ms
timthumb.php
1936 ms
timthumb.php
1901 ms
timthumb.php
2057 ms
timthumb.php
1928 ms
timthumb.php
1998 ms
Core-Values-Hams.jpg
1983 ms
Asset-1@1000x-100.jpg
2486 ms
Touch-1-scaled.jpg
3367 ms
Tech.jpg
2073 ms
pattern-1.svg
1937 ms
timthumb.php
2006 ms
timthumb.php
2049 ms
timthumb.php
2090 ms
timthumb.php
2104 ms
timthumb.php
2520 ms
timthumb.php
2181 ms
timthumb.php
2205 ms
timthumb.php
2550 ms
timthumb.php
3036 ms
timthumb.php
2347 ms
timthumb.php
2368 ms
timthumb.php
2373 ms
Standard-Package.svg
2347 ms
Comprehensive-Package.svg
2369 ms
Executive-Package-Male.svg
2209 ms
Executive-Package-Female-Above-and-Below-45-Same-icon.svg
2253 ms
Senior-Health-Package-Female.svg
2340 ms
timthumb.php
2244 ms
timthumb.php
2293 ms
timthumb.php
2267 ms
timthumb.php
2582 ms
footer-bg.jpg
2337 ms
hamshospital.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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.
hamshospital.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
hamshospital.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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hamshospital.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 Hamshospital.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.
hamshospital.com
Open Graph description is not detected on the main page of HAMS 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: