Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

imne.com

IMNE

Page Load Speed

632 ms in total

First Response

78 ms

Resources Loaded

404 ms

Page Rendered

150 ms

imne.com screenshot

About Website

Welcome to imne.com homepage info - get ready to check IMNE best content right away, or after learning these important things about imne.com

We are educators. We ask the questions that help heal. What do patients need? How can their care be better? As a full-service US-accredited medical education company, we use innovative strategies to t...

Visit imne.com

Key Findings

We analyzed Imne.com page load time and found that the first response time was 78 ms and then it took 554 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster. This domain responded with an error, which can significantly jeopardize Imne.com rating and web reputation

Performance Metrics

imne.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

16/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value3,580 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

imne.com

78 ms

www.imne.com

151 ms

global.css

35 ms

quant.js

12 ms

ga.js

11 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 81% of them (17 requests) were addressed to the original Imne.com, 10% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Edge.quantserve.com. The less responsive or slowest element that took the longest time to load (151 ms) belongs to the original domain Imne.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.7 kB (19%)

Content Size

125.0 kB

After Optimization

101.3 kB

In fact, the total size of Imne.com main page is 125.0 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. 15% of websites need less resources to load. Images take 75.9 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 6.1 kB

  • Original 8.7 kB
  • After minification 7.9 kB
  • After compression 2.6 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 6.1 kB or 70% of the original size.

Image Optimization

-5%

Potential reduce by 3.5 kB

  • Original 75.9 kB
  • After minification 72.3 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. IMNE images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 14.0 kB

  • Original 40.3 kB
  • After minification 40.3 kB
  • After compression 26.3 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 14.0 kB or 35% of the original size.

CSS Optimization

-33%

Potential reduce by 51 B

  • Original 155 B
  • After minification 104 B
  • After compression 104 B

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. Imne.com needs all CSS files to be minified and compressed as it can save up to 51 B or 33% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IMNE. According to our analytics all requests are already optimized.

Accessibility Review

imne.com accessibility score

82

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

imne.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

imne.com SEO score

77

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

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

Social Sharing Optimization

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