Tools & Wizards About Us
nulantic.ca screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

nulantic.ca

Nulantic Water - Commercial water treatment distribution & Supplies

Page Load Speed

4.3 sec in total

First Response

883 ms

Resources Loaded

3.1 sec

Page Rendered

264 ms

nulantic.ca screenshot

About Website

Welcome to nulantic.ca homepage info - get ready to check Nulantic best content right away, or after learning these important things about nulantic.ca

We distribute water and wastewater treatment equipment and supplies in Atlantic Canada like water instrumentation, chemical dosing pumps and water purification systems.

Visit nulantic.ca

Key Findings

We analyzed Nulantic.ca page load time and found that the first response time was 883 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

nulantic.ca performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value19.2 s

0/100

10%

TBT (Total Blocking Time)

Value10,650 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.329

34/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

nulantic.ca

883 ms

css

234 ms

sgr.css

139 ms

style.min.css

234 ms

mediaelementplayer-legacy.min.css

231 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 44% of them (56 requests) were addressed to the original Nulantic.ca, 42% (54 requests) were made to C0.wp.com and 12% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (883 ms) belongs to the original domain Nulantic.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 173.0 kB (25%)

Content Size

686.3 kB

After Optimization

513.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nulantic.ca main page is 686.3 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. 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. CSS take 368.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 74.2 kB

  • Original 86.2 kB
  • After minification 64.3 kB
  • After compression 12.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 21.9 kB, which is 25% 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 74.2 kB or 86% of the original size.

Image Optimization

-20%

Potential reduce by 4.0 kB

  • Original 19.7 kB
  • After minification 15.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, Nulantic needs image optimization as it can save up to 4.0 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 2.1 kB

  • Original 212.0 kB
  • After minification 211.9 kB
  • After compression 209.9 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

-25%

Potential reduce by 92.8 kB

  • Original 368.5 kB
  • After minification 367.6 kB
  • After compression 275.7 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. Nulantic.ca needs all CSS files to be minified and compressed as it can save up to 92.8 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 106 (95%)

Requests Now

111

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nulantic.ca

nulantic.ca

883 ms

css

css

234 ms

sgr.css

sgr.css

139 ms

style.min.css

style.min.css

234 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

231 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

274 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

255 ms

wc-blocks-style.css

wc-blocks-style.css

255 ms

yith-wcbr.css

yith-wcbr.css

217 ms

swiper.css

swiper.css

225 ms

select2.css

select2.css

251 ms

yith-wcbr-shortcode.css

yith-wcbr-shortcode.css

217 ms

settings.css

settings.css

204 ms

button-label.min.css

button-label.min.css

246 ms

style.css

style.css

289 ms

font-awesome.min.css

font-awesome.min.css

361 ms

style.min.css

style.min.css

296 ms

style.css

style.css

365 ms

dripicons.css

dripicons.css

269 ms

stylesheet.min.css

stylesheet.min.css

543 ms

woocommerce.min.css

woocommerce.min.css

345 ms

woocommerce_responsive.min.css

woocommerce_responsive.min.css

378 ms

print.css

print.css

343 ms

style_dynamic.css

style_dynamic.css

371 ms

responsive.min.css

responsive.min.css

407 ms

style_dynamic_responsive.css

style_dynamic_responsive.css

375 ms

js_composer.min.css

js_composer.min.css

481 ms

custom_css.css

custom_css.css

405 ms

ywraq-frontend.css

ywraq-frontend.css

536 ms

style.css

style.css

421 ms

jetpack.css

jetpack.css

268 ms

NUL-Logo-Web-Colour.png

NUL-Logo-Web-Colour.png

458 ms

css

css

249 ms

email-decode.min.js

email-decode.min.js

415 ms

swiper.jquery.min.js

swiper.jquery.min.js

591 ms

select2.full.min.js

select2.full.min.js

260 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

270 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

261 ms

wp-polyfill.min.js

wp-polyfill.min.js

260 ms

hooks.min.js

hooks.min.js

274 ms

yith-wcbr.min.js

yith-wcbr.min.js

452 ms

dummy.png

dummy.png

573 ms

NUL-WebFooterLogo.png

NUL-WebFooterLogo.png

574 ms

js.cookie.min.js

js.cookie.min.js

253 ms

woocommerce.min.js

woocommerce.min.js

253 ms

cart-fragments.min.js

cart-fragments.min.js

251 ms

qode-like.min.js

qode-like.min.js

567 ms

core.min.js

core.min.js

252 ms

accordion.min.js

accordion.min.js

250 ms

menu.min.js

menu.min.js

252 ms

dom-ready.min.js

dom-ready.min.js

261 ms

i18n.min.js

i18n.min.js

260 ms

a11y.min.js

a11y.min.js

260 ms

autocomplete.min.js

autocomplete.min.js

261 ms

controlgroup.min.js

controlgroup.min.js

260 ms

checkboxradio.min.js

checkboxradio.min.js

260 ms

button.min.js

button.min.js

264 ms

datepicker.min.js

datepicker.min.js

264 ms

mouse.min.js

mouse.min.js

263 ms

resizable.min.js

resizable.min.js

270 ms

draggable.min.js

draggable.min.js

270 ms

dialog.min.js

dialog.min.js

269 ms

droppable.min.js

droppable.min.js

279 ms

progressbar.min.js

progressbar.min.js

280 ms

selectable.min.js

selectable.min.js

279 ms

sortable.min.js

sortable.min.js

277 ms

slider.min.js

slider.min.js

279 ms

spinner.min.js

spinner.min.js

278 ms

plugins.js

plugins.js

696 ms

jquery.carouFredSel-6.2.1.min.js

jquery.carouFredSel-6.2.1.min.js

557 ms

lemmon-slider.min.js

lemmon-slider.min.js

556 ms

jquery.fullPage.min.js

jquery.fullPage.min.js

558 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

556 ms

e-202240.js

e-202240.js

236 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

548 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

478 ms

packery-mode.pkgd.min.js

packery-mode.pkgd.min.js

414 ms

jquery.stretch.js

jquery.stretch.js

407 ms

imagesloaded.js

imagesloaded.js

406 ms

rangeslider.min.js

rangeslider.min.js

446 ms

jquery.event.move.js

jquery.event.move.js

443 ms

tooltip.min.js

tooltip.min.js

115 ms

tabs.min.js

tabs.min.js

98 ms

jquery.twentytwenty.js

jquery.twentytwenty.js

408 ms

effect.min.js

effect.min.js

90 ms

effect-blind.min.js

effect-blind.min.js

77 ms

effect-bounce.min.js

effect-bounce.min.js

74 ms

effect-clip.min.js

effect-clip.min.js

68 ms

default_dynamic.js

default_dynamic.js

382 ms

effect-drop.min.js

effect-drop.min.js

61 ms

effect-explode.min.js

effect-explode.min.js

64 ms

effect-fade.min.js

effect-fade.min.js

57 ms

effect-fold.min.js

effect-fold.min.js

57 ms

default.min.js

default.min.js

719 ms

effect-highlight.min.js

effect-highlight.min.js

51 ms

effect-pulsate.min.js

effect-pulsate.min.js

50 ms

effect-size.min.js

effect-size.min.js

47 ms

effect-scale.min.js

effect-scale.min.js

47 ms

effect-shake.min.js

effect-shake.min.js

47 ms

effect-slide.min.js

effect-slide.min.js

48 ms

effect-transfer.min.js

effect-transfer.min.js

48 ms

comment-reply.min.js

comment-reply.min.js

46 ms

custom_js.js

custom_js.js

386 ms

js_composer_front.min.js

js_composer_front.min.js

364 ms

woocommerce.min.js

woocommerce.min.js

386 ms

intersection-observer.js

intersection-observer.js

361 ms

lazy-images.js

lazy-images.js

357 ms

frontend.min.js

frontend.min.js

616 ms

rocket-loader.min.js

rocket-loader.min.js

356 ms

style.css

style.css

352 ms

pxiEyp8kv8JHgFVrJJnedA.woff

pxiEyp8kv8JHgFVrJJnedA.woff

166 ms

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

208 ms

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

205 ms

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

209 ms

pxiGyp8kv8JHgFVrLPTufntG.woff

pxiGyp8kv8JHgFVrLPTufntG.woff

207 ms

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

209 ms

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

189 ms

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

192 ms

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

192 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

161 ms

z7NOdRfiaC4Vd8hhoPzfb5vBTP2D6puoR_4.woff

z7NOdRfiaC4Vd8hhoPzfb5vBTP2D6puoR_4.woff

94 ms

z7NOdRfiaC4Vd8hhoPzfb5vBTP266pumR_4.woff

z7NOdRfiaC4Vd8hhoPzfb5vBTP266pumR_4.woff

94 ms

z7NOdRfiaC4Vd8hhoPzfb5vBTP266puoR_4.woff

z7NOdRfiaC4Vd8hhoPzfb5vBTP266puoR_4.woff

95 ms

z7NOdRfiaC4Vd8hhoPzfb5vBTP1v7ZuoR_4.woff

z7NOdRfiaC4Vd8hhoPzfb5vBTP1v7ZuoR_4.woff

96 ms

z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZuoR_4.woff

z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZuoR_4.woff

97 ms

z7NOdRfiaC4Vd8hhoPzfb5vBTP0D7ZuoR_4.woff

z7NOdRfiaC4Vd8hhoPzfb5vBTP0D7ZuoR_4.woff

96 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

83 ms

sgr.js

sgr.js

106 ms

Accessibility Review

nulantic.ca accessibility score

86

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

nulantic.ca best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

nulantic.ca SEO score

98

Search Engine Optimization Advices

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 Nulantic.ca 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 Nulantic.ca 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

nulantic.ca

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