Tools & Wizards About Us
jotr.in screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

jotr.in

Wolters Kluwer Health

Page Load Speed

1.9 sec in total

First Response

130 ms

Resources Loaded

1.1 sec

Page Rendered

606 ms

jotr.in screenshot

About Website

Visit jotr.in now to see the best up-to-date Jotr content for India and also check out these interesting facts you probably never knew about jotr.in

Journal of Orthopedics, Traumatology and Rehabilitation, Official publication of Central Zone of Indian Orthopaedic Association,India

Visit jotr.in

Key Findings

We analyzed Jotr.in page load time and found that the first response time was 130 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

jotr.in performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value23.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value27.8 s

0/100

25%

SI (Speed Index)

Value25.1 s

0/100

10%

TBT (Total Blocking Time)

Value5,360 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value29.9 s

0/100

10%

Network Requests Diagram

jotr.in

130 ms

www.jotr.in

145 ms

current.css

39 ms

layer.js

55 ms

_getUACode.js

255 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 74% of them (25 requests) were addressed to the original Jotr.in, 18% (6 requests) were made to Medknow.com and 6% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (308 ms) belongs to the original domain Jotr.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.9 kB (62%)

Content Size

185.6 kB

After Optimization

69.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jotr.in main page is 185.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. 25% of websites need less resources to load. Javascripts take 92.8 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 13.8 kB

  • Original 18.7 kB
  • After minification 17.1 kB
  • After compression 4.9 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 13.8 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 1 B

  • Original 1.7 kB
  • After minification 1.7 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. Jotr images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 38.8 kB

  • Original 92.8 kB
  • After minification 80.3 kB
  • After compression 54.1 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 38.8 kB or 42% of the original size.

CSS Optimization

-88%

Potential reduce by 63.3 kB

  • Original 72.4 kB
  • After minification 55.1 kB
  • After compression 9.0 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. Jotr.in needs all CSS files to be minified and compressed as it can save up to 63.3 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (23%)

Requests Now

31

After Optimization

24

  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jotr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

jotr.in

jotr.in

130 ms

www.jotr.in

www.jotr.in

145 ms

current.css

current.css

39 ms

layer.js

layer.js

55 ms

_getUACode.js

_getUACode.js

255 ms

ftr.js

ftr.js

228 ms

_dirj.js

_dirj.js

202 ms

jquery.min.js

jquery.min.js

172 ms

jquery.magnifier_close_but.js

jquery.magnifier_close_but.js

197 ms

commonjsinclude.js

commonjsinclude.js

194 ms

countries.js

countries.js

216 ms

current_l.css

current_l.css

20 ms

current_s.css

current_s.css

112 ms

tmlr.gif

tmlr.gif

174 ms

tmrc.gif

tmrc.gif

164 ms

logo.gif

logo.gif

179 ms

hdrImg1.gif

hdrImg1.gif

267 ms

home.gif

home.gif

263 ms

print.gif

print.gif

263 ms

email.gif

email.gif

261 ms

mbi.gif

mbi.gif

265 ms

tocIcon.gif

tocIcon.gif

262 ms

rssIcon.jpg

rssIcon.jpg

308 ms

submitBtn.gif

submitBtn.gif

269 ms

submt-art-online.gif

submt-art-online.gif

271 ms

subscribe.gif

subscribe.gif

302 ms

site-stats.gif

site-stats.gif

271 ms

join-us.gif

join-us.gif

302 ms

email-alert.gif

email-alert.gif

307 ms

recommnd-journal-icon.gif

recommnd-journal-icon.gif

303 ms

ga.js

ga.js

139 ms

cover.png

cover.png

258 ms

fri.gif

fri.gif

260 ms

__utm.gif

__utm.gif

75 ms

Accessibility Review

jotr.in accessibility score

67

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

jotr.in best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

jotr.in SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jotr.in 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 Jotr.in main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

jotr.in

Open Graph description is not detected on the main page of Jotr. 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: