5 sec in total
1.2 sec
3.7 sec
121 ms
Click here to check amazing St John S content for India. Otherwise, check out these important facts you probably never knew about stjohns.in
Visit stjohns.inWe analyzed Stjohns.in page load time and found that the first response time was 1.2 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
stjohns.in performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value27.4 s
0/100
25%
Value10.4 s
8/100
10%
Value770 ms
38/100
30%
Value1.356
0/100
15%
Value15.2 s
7/100
10%
1218 ms
785 ms
6 ms
48 ms
735 ms
Our browser made a total of 22 requests to load all elements on the main page. We found that 86% of them (19 requests) were addressed to the original Stjohns.in, 9% (2 requests) were made to Ajax.googleapis.com and 5% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Stjohns.in.
Page size can be reduced by 113.8 kB (25%)
451.6 kB
337.8 kB
In fact, the total size of Stjohns.in main page is 451.6 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. Images take 333.3 kB which makes up the majority of the site volume.
Potential reduce by 12.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. This page needs HTML code to be minified as it can gain 7.2 kB, which is 49% 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 12.4 kB or 84% of the original size.
Potential reduce by 32.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. St John S images are well optimized though.
Potential reduce by 61.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 61.7 kB or 65% of the original size.
Potential reduce by 6.8 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. Stjohns.in needs all CSS files to be minified and compressed as it can save up to 6.8 kB or 77% of the original size.
Number of requests can be reduced by 4 (19%)
21
17
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of St John S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
stjohns.in
1218 ms
sji_styles.css
785 ms
jquery-1.5.2.js
6 ms
jquery-ui.js
48 ms
style.css
735 ms
jquery.js
1714 ms
jquery-ui.css
57 ms
wowslider.js
492 ms
script.js
715 ms
top_bg.png
248 ms
st_johns_logo.png
711 ms
link_sep.png
253 ms
hm_line.png
263 ms
hm_vis1.jpg
977 ms
hm_vis2.jpg
960 ms
hm_vis3.jpg
731 ms
hm_vis4.jpg
1181 ms
hm_vis5.jpg
747 ms
hm_vis6.jpg
943 ms
view_all.png
966 ms
click_details.png
955 ms
arrows.png
1144 ms
stjohns.in 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
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.
stjohns.in 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
stjohns.in 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 Stjohns.in 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 Stjohns.in 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.
stjohns.in
Open Graph description is not detected on the main page of St John S. 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: