5.1 sec in total
1.3 sec
3.3 sec
531 ms
Visit scannix.com now to see the best up-to-date Scannix content and also check out these interesting facts you probably never knew about scannix.com
Your partner for : Nuclear medicine - Industry - Research & Development - Waste management - Radiation monitoring - Radiopharma
Visit scannix.comWe analyzed Scannix.com page load time and found that the first response time was 1.3 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
scannix.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value12.4 s
0/100
25%
Value9.3 s
13/100
10%
Value910 ms
31/100
30%
Value0.292
41/100
15%
Value9.9 s
27/100
10%
1280 ms
28 ms
280 ms
308 ms
328 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 58% of them (52 requests) were addressed to the original Scannix.com, 38% (34 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Scannix.com.
Page size can be reduced by 627.0 kB (26%)
2.4 MB
1.8 MB
In fact, the total size of Scannix.com main page is 2.4 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 285.1 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 285.1 kB or 86% of the original size.
Potential reduce by 44.4 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. Scannix images are well optimized though.
Potential reduce by 263.7 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 263.7 kB or 48% of the original size.
Potential reduce by 33.9 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. Scannix.com needs all CSS files to be minified and compressed as it can save up to 33.9 kB or 35% of the original size.
Number of requests can be reduced by 35 (65%)
54
19
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Scannix. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.scannix.com
1280 ms
css
28 ms
global.css
280 ms
styles.css
308 ms
cookieblocker.min.css
328 ms
dflip.min.css
440 ms
css
21 ms
frontend-lite.min.css
372 ms
swiper.min.css
288 ms
post-5242.css
308 ms
global.css
323 ms
choices.min.css
346 ms
css
23 ms
smartslider.min.css
385 ms
css
23 ms
jquery.min.js
496 ms
jquery-migrate.min.js
419 ms
circle-progress.js
442 ms
global.js
463 ms
frontend-gtag.min.js
486 ms
n2.min.js
575 ms
smartslider-frontend.min.js
635 ms
ss-simple.min.js
577 ms
smartslider-backgroundanimation.min.js
577 ms
w-arrow-image.min.js
596 ms
w-bullet.min.js
601 ms
embed-lite.min.js
553 ms
index.js
570 ms
index.js
604 ms
scripts.min.js
716 ms
smoothscroll.js
630 ms
dflip.min.js
741 ms
jquery.fitvids.js
671 ms
common.js
688 ms
smush-lazy-load.min.js
711 ms
complianz.min.js
740 ms
motion-effects.js
773 ms
LOGO-SCANNIX-WEB.png
810 ms
20240427_133714-scaled.jpg
735 ms
AD-automess-scannix-2.jpg
484 ms
AD-automess-scannix.jpg
590 ms
H3D.jpg
511 ms
FLIR-BIS.webp
442 ms
VIDERAY.jpg
633 ms
SYSCADE-31.jpg
588 ms
HEQGE9827-scaled.jpg
697 ms
20240427_133714-scaled.jpg
691 ms
AD-automess-scannix-2.jpg
721 ms
AD-automess-scannix.jpg
736 ms
H3D.jpg
803 ms
FLIR-BIS.webp
807 ms
VIDERAY.jpg
827 ms
SYSCADE-31.jpg
848 ms
HEQGE9827-scaled.jpg
868 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTo3ig.ttf
38 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTo3ig.ttf
29 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTo3ig.ttf
38 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDshdTo3ig.ttf
37 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTo3ig.ttf
38 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTo3ig.ttf
37 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTo3ig.ttf
57 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTo3ig.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
56 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
58 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
62 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
62 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
61 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
59 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
61 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
62 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
73 ms
i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHdZTPpYfy.ttf
73 ms
i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHTJTPpYfy.ttf
73 ms
i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHK5TPpYfy.ttf
62 ms
i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHApTPpYfy.ttf
72 ms
i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHmZPPpYfy.ttf
72 ms
i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHq5PPpYfy.ttf
74 ms
i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSH9ZPPpYfy.ttf
74 ms
i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHK5PPpYfy.ttf
73 ms
i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHq5LPpYfy.ttf
74 ms
modules.woff
862 ms
style.min.css
102 ms
scannix.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
scannix.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
scannix.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Scannix.com 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 Scannix.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.
scannix.com
Open Graph data is detected on the main page of Scannix. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: