Tools & Wizards About Us
numrx.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

numrx.com

Accueil - NUM RX - Informatique et Radiologie numérique

Page Load Speed

4.1 sec in total

First Response

706 ms

Resources Loaded

2.6 sec

Page Rendered

762 ms

numrx.com screenshot

About Website

Click here to check amazing NUM RX content. Otherwise, check out these important facts you probably never knew about numrx.com

NUM RX Distributeur Expert Agréé en Informatique, Radiologie et Applications numériques au service des chirurgiens dentistes et cabinets dentaires

Visit numrx.com

Key Findings

We analyzed Numrx.com page load time and found that the first response time was 706 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

numrx.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value530 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

www.numrx.com

706 ms

js

65 ms

css-b30fc-22274.css

155 ms

css-32377-22275.css

236 ms

css

40 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 67% of them (22 requests) were addressed to the original Numrx.com, 15% (5 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (721 ms) belongs to the original domain Numrx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 472.3 kB (5%)

Content Size

9.1 MB

After Optimization

8.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Numrx.com main page is 9.1 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. 40% of websites need less resources to load. Images take 8.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 33.2 kB

  • Original 42.3 kB
  • After minification 37.0 kB
  • After compression 9.0 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 5.3 kB, which is 13% 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 33.2 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 437.0 kB

  • Original 8.8 MB
  • After minification 8.4 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. NUM RX images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.1 kB

  • Original 188.7 kB
  • After minification 188.7 kB
  • After compression 187.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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 1.1 kB

  • Original 51.4 kB
  • After minification 51.4 kB
  • After compression 50.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. Numrx.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (38%)

Requests Now

26

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.numrx.com

www.numrx.com

706 ms

js

js

65 ms

css-b30fc-22274.css

css-b30fc-22274.css

155 ms

css-32377-22275.css

css-32377-22275.css

236 ms

css

css

40 ms

css

css

59 ms

css-a30ce-22275.css

css-a30ce-22275.css

249 ms

js-5bb5a-66687.js

js-5bb5a-66687.js

424 ms

acymailing_module.js

acymailing_module.js

253 ms

js-625e7-66694.js

js-625e7-66694.js

396 ms

system.css

system.css

93 ms

hqdefault.jpg

hqdefault.jpg

154 ms

logo-numrx.png

logo-numrx.png

156 ms

logo-numrx-small.png

logo-numrx-small.png

163 ms

Slideshow-6.jpg

Slideshow-6.jpg

487 ms

Slideshow-1.jpg

Slideshow-1.jpg

603 ms

Slideshow-test.jpg

Slideshow-test.jpg

471 ms

Slideshow-7-V2.jpg

Slideshow-7-V2.jpg

620 ms

Slideshow-8-V2.jpg

Slideshow-8-V2.jpg

385 ms

evolution.jpg

evolution.jpg

721 ms

VISUELS_LES_3_CLES_Plan_de_travail_1.jpg

VISUELS_LES_3_CLES_Plan_de_travail_1.jpg

621 ms

adf_2022.png

adf_2022.png

551 ms

1.png

1.png

656 ms

image-NUMRX.jpg

image-NUMRX.jpg

711 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

139 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

157 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

173 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

174 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

173 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

683 ms

iframe_api

iframe_api

168 ms

slash-bg.png

slash-bg.png

548 ms

www-widgetapi.js

www-widgetapi.js

4 ms

Accessibility Review

numrx.com accessibility score

61

Accessibility Issues

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

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> 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

numrx.com best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

numrx.com SEO score

86

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

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Numrx.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Numrx.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

numrx.com

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