Tools & Wizards About Us
pmr.in screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

pmr.in

PMR Footcare, Knee & Body Support | Paragon Mobility Rehab

Page Load Speed

3.3 sec in total

First Response

153 ms

Resources Loaded

2.9 sec

Page Rendered

238 ms

pmr.in screenshot

About Website

Click here to check amazing PMR content for India. Otherwise, check out these important facts you probably never knew about pmr.in

Paragon Mobility Rehab is the leading manufacturer & supplier of medical equipment like knee support brace, silicon foot care, compression socks, body supports.

Visit pmr.in

Key Findings

We analyzed Pmr.in page load time and found that the first response time was 153 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

pmr.in performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value18.9 s

0/100

25%

SI (Speed Index)

Value18.3 s

0/100

10%

TBT (Total Blocking Time)

Value3,350 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.615

10/100

15%

TTI (Time to Interactive)

Value33.4 s

0/100

10%

Network Requests Diagram

pmr.in

153 ms

www.pmr.in

631 ms

calendar.css

126 ms

styles-m.css

295 ms

scroll.css

191 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 80% of them (82 requests) were addressed to the original Pmr.in, 8% (8 requests) were made to Youtube.com and 4% (4 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (942 ms) belongs to the original domain Pmr.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 263.8 kB (14%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pmr.in main page is 2.0 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. Only a small number of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 112.8 kB

  • Original 128.7 kB
  • After minification 92.7 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 35.9 kB, which is 28% 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 112.8 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 4.2 kB

  • Original 1.2 MB
  • After minification 1.2 MB

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. PMR images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 133.6 kB

  • Original 411.6 kB
  • After minification 410.0 kB
  • After compression 278.0 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 133.6 kB or 32% of the original size.

CSS Optimization

-8%

Potential reduce by 13.2 kB

  • Original 168.4 kB
  • After minification 168.4 kB
  • After compression 155.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. Pmr.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 63 (68%)

Requests Now

93

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pmr.in

pmr.in

153 ms

www.pmr.in

www.pmr.in

631 ms

calendar.css

calendar.css

126 ms

styles-m.css

styles-m.css

295 ms

scroll.css

scroll.css

191 ms

owl.carousel.css

owl.carousel.css

201 ms

owl.theme.css

owl.theme.css

203 ms

owl.transitions.css

owl.transitions.css

202 ms

jquery.fancybox.css

jquery.fancybox.css

202 ms

font-awesome.min.css

font-awesome.min.css

256 ms

styles.css

styles.css

271 ms

styles-l.css

styles-l.css

351 ms

require.js

require.js

348 ms

mixins.js

mixins.js

271 ms

requirejs-config.js

requirejs-config.js

320 ms

polyfill.js

polyfill.js

335 ms

scroll.js

scroll.js

336 ms

home-slider.js

home-slider.js

368 ms

styles.css

styles.css

388 ms

js

js

61 ms

js

js

106 ms

whitedemo.css

whitedemo.css

413 ms

jquery.js

jquery.js

192 ms

jquery.mobile.custom.js

jquery.mobile.custom.js

88 ms

common.js

common.js

87 ms

dataPost.js

dataPost.js

87 ms

bootstrap.js

bootstrap.js

87 ms

fbevents.js

fbevents.js

34 ms

gtm.js

gtm.js

66 ms

peragon_logo.png

peragon_logo.png

88 ms

Banner-1.jpg

Banner-1.jpg

736 ms

Banner-2.jpg

Banner-2.jpg

736 ms

Banner-3.jpg

Banner-3.jpg

735 ms

paragon-polycentric-knee-caliper-premium-l3_1_1.jpg

paragon-polycentric-knee-caliper-premium-l3_1_1.jpg

123 ms

0000022_paragon-ultimate-knee-brace_2.jpeg

0000022_paragon-ultimate-knee-brace_2.jpeg

140 ms

0000026_paragon-knee-brace-supra_1_1.jpeg

0000026_paragon-knee-brace-supra_1_1.jpeg

197 ms

0000120_cock-up-splint-neoprene.jpeg

0000120_cock-up-splint-neoprene.jpeg

210 ms

0000059_paragon-ozone-food-guard.jpeg

0000059_paragon-ozone-food-guard.jpeg

210 ms

0000141_paragon-hot-n-cold-gel-pack-deluxe-xl_550.jpeg

0000141_paragon-hot-n-cold-gel-pack-deluxe-xl_550.jpeg

276 ms

0000081_paragon-below-knee-stocking_550.jpeg

0000081_paragon-below-knee-stocking_550.jpeg

304 ms

0000150_paragon-silicone-gel-heel-cup_550.jpeg

0000150_paragon-silicone-gel-heel-cup_550.jpeg

316 ms

paragon-polycentric-knee-caliper-supra-b4-for-both-legs-250x250.jpg

paragon-polycentric-knee-caliper-supra-b4-for-both-legs-250x250.jpg

731 ms

0000021_paragon-ultimate-knee-brace.jpeg

0000021_paragon-ultimate-knee-brace.jpeg

731 ms

avticon.png

avticon.png

730 ms

peragon_logo_1.png

peragon_logo_1.png

731 ms

ajax-loader.gif

ajax-loader.gif

731 ms

translate-inline.js

translate-inline.js

730 ms

mage-translation-dictionary.js

mage-translation-dictionary.js

732 ms

responsive.js

responsive.js

730 ms

theme.js

theme.js

794 ms

owl.carousel.js

owl.carousel.js

793 ms

jquery.js

jquery.js

778 ms

opensans-400.woff

opensans-400.woff

769 ms

opensans-300.woff

opensans-300.woff

769 ms

opensans-600.woff

opensans-600.woff

942 ms

opensans-700.woff

opensans-700.woff

850 ms

domReady.js

domReady.js

799 ms

main.js

main.js

890 ms

bootstrap.js

bootstrap.js

797 ms

template.js

template.js

888 ms

confirm.js

confirm.js

889 ms

widget.js

widget.js

887 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

888 ms

Luma-Icons.woff

Luma-Icons.woff

883 ms

stripes.png

stripes.png

877 ms

eH6oIFV_frY

eH6oIFV_frY

115 ms

vH_WzyShAl8

vH_WzyShAl8

120 ms

yCns8iUbw_E

yCns8iUbw_E

499 ms

LkKo-GkACho

LkKo-GkACho

180 ms

default

default

468 ms

footer-stripeswhite.png

footer-stripeswhite.png

812 ms

jquery-migrate.js

jquery-migrate.js

793 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

29 ms

base.js

base.js

71 ms

ad_status.js

ad_status.js

416 ms

embed.js

embed.js

152 ms

id

id

96 ms

Create

Create

148 ms

Create

Create

277 ms

Create

Create

280 ms

Create

Create

278 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

111 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

119 ms

print.css

print.css

104 ms

translate.js

translate.js

92 ms

text.js

text.js

252 ms

tabs.js

tabs.js

251 ms

smart-keyboard-handler.js

smart-keyboard-handler.js

213 ms

mage.js

mage.js

211 ms

ie-class-fixer.js

ie-class-fixer.js

212 ms

knockout.js

knockout.js

212 ms

knockout-es5.js

knockout-es5.js

213 ms

underscore.js

underscore.js

213 ms

modal.js

modal.js

209 ms

dialog.js

dialog.js

172 ms

jquery-ui.js

jquery-ui.js

173 ms

matchMedia.js

matchMedia.js

173 ms

engine.js

engine.js

261 ms

bootstrap.js

bootstrap.js

262 ms

observable_array.js

observable_array.js

261 ms

bound-nodes.js

bound-nodes.js

262 ms

scripts.js

scripts.js

262 ms

Accessibility Review

pmr.in accessibility score

85

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pmr.in best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

pmr.in SEO score

93

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pmr.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 Pmr.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.

Social Sharing Optimization

pmr.in

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