Tools & Wizards About Us
oxistat.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

oxistat.com

Fungal Infection Lotion | OXISTAT® (oxiconazole nitrate) Lotion

Page Load Speed

4.7 sec in total

First Response

1.4 sec

Resources Loaded

3.1 sec

Page Rendered

185 ms

oxistat.com screenshot

About Website

Visit oxistat.com now to see the best up-to-date OXISTAT content and also check out these interesting facts you probably never knew about oxistat.com

APPLY THE POWER OF OXISTAT LOTION! Athlete’s foot*, jock itch, and ringworm are no match for OXISTAT® Lotion

Visit oxistat.com

Key Findings

We analyzed Oxistat.com page load time and found that the first response time was 1.4 sec and then it took 3.3 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

oxistat.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.2 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

www.oxistat.com

1393 ms

pum-site-styles.css

252 ms

style.css

189 ms

637cab38a900431445eff09fb3307e52.min.css

632 ms

jquery.min.js

318 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 99% of them (71 requests) were addressed to the original Oxistat.com, 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Oxistat.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (59%)

Content Size

2.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oxistat.com main page is 2.9 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. 35% of websites need less resources to load. CSS take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 127.0 kB

  • Original 147.3 kB
  • After minification 145.9 kB
  • After compression 20.3 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 127.0 kB or 86% of the original size.

Image Optimization

-13%

Potential reduce by 112.6 kB

  • Original 887.3 kB
  • After minification 774.7 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. Obviously, OXISTAT needs image optimization as it can save up to 112.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 477.8 kB

  • Original 684.3 kB
  • After minification 684.2 kB
  • After compression 206.5 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 477.8 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 974.0 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 163.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. Oxistat.com needs all CSS files to be minified and compressed as it can save up to 974.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (86%)

Requests Now

70

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.oxistat.com

www.oxistat.com

1393 ms

pum-site-styles.css

pum-site-styles.css

252 ms

style.css

style.css

189 ms

637cab38a900431445eff09fb3307e52.min.css

637cab38a900431445eff09fb3307e52.min.css

632 ms

jquery.min.js

jquery.min.js

318 ms

jquery-migrate.min.js

jquery-migrate.min.js

191 ms

core.min.js

core.min.js

104 ms

pum-site-scripts.js

pum-site-scripts.js

213 ms

awb-tabs-widget.js

awb-tabs-widget.js

93 ms

awb-vertical-menu-widget.js

awb-vertical-menu-widget.js

128 ms

cssua.js

cssua.js

149 ms

modernizr.js

modernizr.js

156 ms

fusion.js

fusion.js

192 ms

swiper.js

swiper.js

399 ms

bootstrap.transition.js

bootstrap.transition.js

216 ms

bootstrap.tooltip.js

bootstrap.tooltip.js

219 ms

jquery.requestAnimationFrame.js

jquery.requestAnimationFrame.js

255 ms

jquery.easing.js

jquery.easing.js

275 ms

jquery.fitvids.js

jquery.fitvids.js

279 ms

jquery.flexslider.js

jquery.flexslider.js

283 ms

jquery.ilightbox.js

jquery.ilightbox.js

322 ms

jquery.mousewheel.js

jquery.mousewheel.js

338 ms

jquery.fade.js

jquery.fade.js

342 ms

fusion-equal-heights.js

fusion-equal-heights.js

346 ms

fusion-parallax.js

fusion-parallax.js

385 ms

fusion-video-general.js

fusion-video-general.js

400 ms

fusion-video-bg.js

fusion-video-bg.js

406 ms

fusion-lightbox.js

fusion-lightbox.js

411 ms

fusion-tooltip.js

fusion-tooltip.js

449 ms

fusion-sharing-box.js

fusion-sharing-box.js

460 ms

jquery.sticky-kit.js

jquery.sticky-kit.js

549 ms

fusion-youtube.js

fusion-youtube.js

549 ms

vimeoPlayer.js

vimeoPlayer.js

550 ms

fusion-general-global.js

fusion-general-global.js

550 ms

avada-general-footer.js

avada-general-footer.js

550 ms

avada-quantity.js

avada-quantity.js

550 ms

avada-crossfade-images.js

avada-crossfade-images.js

551 ms

avada-select.js

avada-select.js

531 ms

avada-live-search.js

avada-live-search.js

530 ms

fusion-alert.js

fusion-alert.js

532 ms

css

css

29 ms

awb-off-canvas.js

awb-off-canvas.js

509 ms

fusion-button.js

fusion-button.js

504 ms

fusion-animations.js

fusion-animations.js

469 ms

fusion-column-legacy.js

fusion-column-legacy.js

466 ms

awb-background-slider.js

awb-background-slider.js

464 ms

fusion-menu.js

fusion-menu.js

487 ms

awb-mega-menu.js

awb-mega-menu.js

462 ms

fusion-flexslider.js

fusion-flexslider.js

446 ms

jquery.textillate.js

jquery.textillate.js

441 ms

fusion-title.js

fusion-title.js

444 ms

fusion-content-boxes.js

fusion-content-boxes.js

414 ms

fusion-legacy-mega-menu.js

fusion-legacy-mega-menu.js

431 ms

fusion-container.js

fusion-container.js

438 ms

avada-drop-down.js

avada-drop-down.js

437 ms

avada-to-top.js

avada-to-top.js

398 ms

avada-custom-header.js

avada-custom-header.js

389 ms

bootstrap.scrollspy.js

bootstrap.scrollspy.js

390 ms

avada-scrollspy.js

avada-scrollspy.js

423 ms

fusion-responsive-typography.js

fusion-responsive-typography.js

395 ms

fusion-scroll-to-anchor.js

fusion-scroll-to-anchor.js

385 ms

fusion-video.js

fusion-video.js

381 ms

fusion-column.js

fusion-column.js

384 ms

oxistat-header-logo.jpg

oxistat-header-logo.jpg

299 ms

oxistat-header-logo-m.gif

oxistat-header-logo-m.gif

315 ms

infection-feet.0d27c68.png

infection-feet.0d27c68.png

321 ms

oxistat2.png

oxistat2.png

302 ms

infection-arm.fc239cb.png

infection-arm.fc239cb.png

298 ms

dot.gif

dot.gif

303 ms

footer-logo.35dd8ff.jpg

footer-logo.35dd8ff.jpg

309 ms

pedis.a525ceb.png

pedis.a525ceb.png

347 ms

awb-icons.woff

awb-icons.woff

362 ms

Accessibility Review

oxistat.com accessibility score

97

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.

Best Practices

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

SEO Factors

oxistat.com SEO score

86

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

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

oxistat.com

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