Tools & Wizards About Us
xenex.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

xenex.com

Xenex Microbial Reduction

Page Load Speed

1.8 sec in total

First Response

69 ms

Resources Loaded

1.2 sec

Page Rendered

528 ms

xenex.com screenshot

About Website

Visit xenex.com now to see the best up-to-date Xenex content for United States and also check out these interesting facts you probably never knew about xenex.com

Xenex’s pulsed, high energy, broad spectrum UV light technology is uniquely lethal to microorganisms – it’s 4300x more intense in peak power than a mercury lamp.

Visit xenex.com

Key Findings

We analyzed Xenex.com page load time and found that the first response time was 69 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

xenex.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

xenex.com

69 ms

xenex.com

183 ms

font-awesome.min.css

36 ms

mts-notification-bar-public.css

70 ms

cookie-law-info-public.css

92 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 94% of them (74 requests) were addressed to the original Xenex.com, 3% (2 requests) were made to Googletagmanager.com and 1% (1 request) were made to Script.crazyegg.com. The less responsive or slowest element that took the longest time to load (464 ms) belongs to the original domain Xenex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 359.6 kB (20%)

Content Size

1.8 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xenex.com main page is 1.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 277.2 kB

  • Original 315.9 kB
  • After minification 285.7 kB
  • After compression 38.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 277.2 kB or 88% of the original size.

Image Optimization

-6%

Potential reduce by 65.3 kB

  • Original 1.0 MB
  • After minification 953.9 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. Xenex images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 13.1 kB

  • Original 296.2 kB
  • After minification 296.2 kB
  • After compression 283.1 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 3.9 kB

  • Original 171.3 kB
  • After minification 171.3 kB
  • After compression 167.4 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. Xenex.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 65 (87%)

Requests Now

75

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xenex.com

xenex.com

69 ms

xenex.com

xenex.com

183 ms

font-awesome.min.css

font-awesome.min.css

36 ms

mts-notification-bar-public.css

mts-notification-bar-public.css

70 ms

cookie-law-info-public.css

cookie-law-info-public.css

92 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

95 ms

grid-system.css

grid-system.css

93 ms

style.css

style.css

130 ms

header-secondary-nav.css

header-secondary-nav.css

96 ms

element-milestone.css

element-milestone.css

100 ms

4f008a4e3b30.google-fonts.min.css

4f008a4e3b30.google-fonts.min.css

123 ms

responsive.css

responsive.css

125 ms

flickity.css

flickity.css

126 ms

skin-material.css

skin-material.css

137 ms

menu-dynamic.css

menu-dynamic.css

140 ms

js_composer.min.css

js_composer.min.css

155 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

190 ms

style.css

style.css

161 ms

pulse.min.css

pulse.min.css

158 ms

bounce.min.css

bounce.min.css

160 ms

cp-module-main.css

cp-module-main.css

162 ms

modal.min.css

modal.min.css

185 ms

6de09eb019d5.google-fonts.min.css

6de09eb019d5.google-fonts.min.css

196 ms

slick.css

slick.css

197 ms

menu_style.css

menu_style.css

196 ms

dev_style.css

dev_style.css

197 ms

dev_landing.css

dev_landing.css

216 ms

clever-mega-menu-theme-default-461836.css

clever-mega-menu-theme-default-461836.css

218 ms

style.min.css

style.min.css

221 ms

typicons.min.css

typicons.min.css

221 ms

vc_material.min.css

vc_material.min.css

223 ms

jquery.min.js

jquery.min.js

256 ms

jquery.cookie.js

jquery.cookie.js

248 ms

mts-notification-bar-public.js

mts-notification-bar-public.js

249 ms

cookie-law-info-public.js

cookie-law-info-public.js

253 ms

cookie-law-info-ccpa.js

cookie-law-info-ccpa.js

253 ms

js

js

81 ms

js

js

133 ms

1577.js

1577.js

48 ms

loader.js

loader.js

72 ms

v4.js

v4.js

28 ms

slick.min.js

slick.min.js

274 ms

front_style.css

front_style.css

274 ms

first_order_2.min.css

first_order_2.min.css

252 ms

style-non-critical.css

style-non-critical.css

226 ms

jquery.fancybox.css

jquery.fancybox.css

204 ms

core.css

core.css

203 ms

slide-out-right-material.css

slide-out-right-material.css

253 ms

slide-out-right-hover.css

slide-out-right-hover.css

252 ms

cookie-law-info-table.css

cookie-law-info-table.css

248 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

224 ms

priority.js

priority.js

222 ms

transit.min.js

transit.min.js

221 ms

waypoints.js

waypoints.js

213 ms

imagesLoaded.min.js

imagesLoaded.min.js

275 ms

hoverintent.min.js

hoverintent.min.js

274 ms

jquery.fancybox.js

jquery.fancybox.js

260 ms

anime.min.js

anime.min.js

255 ms

flickity.js

flickity.js

251 ms

superfish.js

superfish.js

252 ms

init.js

init.js

304 ms

touchswipe.min.js

touchswipe.min.js

226 ms

select2.min.js

select2.min.js

265 ms

lazyload.min.js

lazyload.min.js

219 ms

clever-mega-menu.min.js

clever-mega-menu.min.js

218 ms

js_composer_front.min.js

js_composer_front.min.js

261 ms

cp-module-main.js

cp-module-main.js

267 ms

modal.min.js

modal.min.js

243 ms

logo-16.svg

logo-16.svg

192 ms

Frame-546.jpg

Frame-546.jpg

197 ms

Frame-547.jpg

Frame-547.jpg

198 ms

Frame-548-1.jpg

Frame-548-1.jpg

198 ms

Image_20230811_125455_557.jpeg

Image_20230811_125455_557.jpeg

199 ms

LightStrike-in-Hospital-Room-scaled.jpeg

LightStrike-in-Hospital-Room-scaled.jpeg

463 ms

LS-PLUS-TRIO.png

LS-PLUS-TRIO.png

464 ms

Circle-Bot-Top-mod.png

Circle-Bot-Top-mod.png

389 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

273 ms

icomoon.woff

icomoon.woff

273 ms

91520b7c67c9.google-fonts.min.css

91520b7c67c9.google-fonts.min.css

48 ms

Accessibility Review

xenex.com accessibility score

89

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

xenex.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

xenex.com SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

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

xenex.com

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