Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

mprex.in

Home - MPREX

Page Load Speed

16.1 sec in total

First Response

607 ms

Resources Loaded

14.5 sec

Page Rendered

929 ms

mprex.in screenshot

About Website

Welcome to mprex.in homepage info - get ready to check MPREX best content right away, or after learning these important things about mprex.in

Looking For Top Clinical Trial Companies In India Mprex Is One Of The Best Clinical Research Organization In India At Pune.

Visit mprex.in

Key Findings

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

Performance Metrics

mprex.in performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value20.2 s

0/100

25%

SI (Speed Index)

Value30.5 s

0/100

10%

TBT (Total Blocking Time)

Value4,040 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.366

29/100

15%

TTI (Time to Interactive)

Value36.4 s

0/100

10%

Network Requests Diagram

mprex.in

607 ms

mprex.in

4940 ms

js

62 ms

font-awesome.min.css

29 ms

style.min.css

769 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 73% of them (106 requests) were addressed to the original Mprex.in, 8% (12 requests) were made to Embed.tawk.to and 4% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Mprex.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (17%)

Content Size

7.0 MB

After Optimization

5.8 MB

In fact, the total size of Mprex.in main page is 7.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 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 242.9 kB

  • Original 281.3 kB
  • After minification 272.3 kB
  • After compression 38.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 242.9 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 305.1 kB

  • Original 5.2 MB
  • After minification 4.8 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. MPREX images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 329.4 kB

  • Original 928.0 kB
  • After minification 928.0 kB
  • After compression 598.6 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 329.4 kB or 35% of the original size.

CSS Optimization

-52%

Potential reduce by 330.3 kB

  • Original 638.0 kB
  • After minification 636.8 kB
  • After compression 307.7 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. Mprex.in needs all CSS files to be minified and compressed as it can save up to 330.3 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 85 (64%)

Requests Now

133

After Optimization

48

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

Accessibility Review

mprex.in accessibility score

87

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

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

mprex.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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

mprex.in SEO score

97

Search Engine Optimization Advices

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

    UTF-8

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

Open Graph data is detected on the main page of MPREX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: