Tools & Wizards About Us
wellsec.co.nz screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

wellsec.co.nz

Wellington Security, Alarm Monitoring, CCTV & Electrical Services

Page Load Speed

8.9 sec in total

First Response

1.2 sec

Resources Loaded

7.2 sec

Page Rendered

482 ms

wellsec.co.nz screenshot

About Website

Click here to check amazing Wellsec content. Otherwise, check out these important facts you probably never knew about wellsec.co.nz

Wellington Security, Alarm and CCTV Systems to protect what matters most to you. Call now for your FREE Security Check.

Visit wellsec.co.nz

Key Findings

We analyzed Wellsec.co.nz page load time and found that the first response time was 1.2 sec and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

wellsec.co.nz performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.303

39/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

wellingtonsecurity.co.nz

1181 ms

pagenavi-css.css

424 ms

main.min.css

849 ms

cryptx.min.js

637 ms

jquery.min.js

852 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wellsec.co.nz, 2% (1 request) were made to Google.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Wellingtonsecurity.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.9 kB (8%)

Content Size

718.6 kB

After Optimization

659.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wellsec.co.nz main page is 718.6 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. 40% of websites need less resources to load. Images take 430.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 57.8 kB

  • Original 71.5 kB
  • After minification 63.6 kB
  • After compression 13.7 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 7.9 kB, which is 11% 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 57.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 39 B

  • Original 430.3 kB
  • After minification 430.2 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. Wellsec images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

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

Requests Breakdown

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

Requests Now

40

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wellingtonsecurity.co.nz

wellingtonsecurity.co.nz

1181 ms

pagenavi-css.css

pagenavi-css.css

424 ms

main.min.css

main.min.css

849 ms

cryptx.min.js

cryptx.min.js

637 ms

jquery.min.js

jquery.min.js

852 ms

jquery-migrate.min.js

jquery-migrate.min.js

640 ms

vendor.min.js

vendor.min.js

645 ms

main.min.js

main.min.js

433 ms

api.js

api.js

32 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

679 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

679 ms

wp-polyfill.min.js

wp-polyfill.min.js

860 ms

index.js

index.js

861 ms

hooks.min.js

hooks.min.js

862 ms

i18n.min.js

i18n.min.js

863 ms

index.js

index.js

864 ms

index.js

index.js

864 ms

gtm.js

gtm.js

91 ms

logo-wse-tag-tight.png

logo-wse-tag-tight.png

419 ms

5-year-workmanship-warranty.png

5-year-workmanship-warranty.png

418 ms

1170x350-sliders_c_offer-info-1400x440.jpg

1170x350-sliders_c_offer-info-1400x440.jpg

629 ms

1170x350-sliders_break-in_b-1400x440.jpg

1170x350-sliders_break-in_b-1400x440.jpg

422 ms

slide-2-1400x440.jpg

slide-2-1400x440.jpg

631 ms

home-security-600x300.jpg

home-security-600x300.jpg

423 ms

commercial-security-systems.jpg

commercial-security-systems.jpg

633 ms

cctv-systems.jpg

cctv-systems.jpg

633 ms

unnamed-600x300.jpg

unnamed-600x300.jpg

636 ms

home-audio-visual.jpg

home-audio-visual.jpg

637 ms

bathroom-led-strip-lighting.jpg

bathroom-led-strip-lighting.jpg

844 ms

logo-bosch@2x.png

logo-bosch@2x.png

845 ms

logo-paradox@2x.png

logo-paradox@2x.png

849 ms

logo-micron@2x.png

logo-micron@2x.png

848 ms

logo-dsc@2x.png

logo-dsc@2x.png

851 ms

logo-axis@2x.png

logo-axis@2x.png

850 ms

logo-hikvision@2x.png

logo-hikvision@2x.png

1058 ms

logo-sony@2x.png

logo-sony@2x.png

1059 ms

logo-milestone@2x.png

logo-milestone@2x.png

1067 ms

logo-uniview@2x.png

logo-uniview@2x.png

1063 ms

angle-down.svg

angle-down.svg

1050 ms

home-security-electrical.jpg

home-security-electrical.jpg

1257 ms

Raleway-Regular.ttf

Raleway-Regular.ttf

1466 ms

Raleway-SemiBold.ttf

Raleway-SemiBold.ttf

1471 ms

recaptcha__en.js

recaptcha__en.js

24 ms

Montserrat-Bold.ttf

Montserrat-Bold.ttf

1609 ms

Accessibility Review

wellsec.co.nz accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

wellsec.co.nz 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

wellsec.co.nz SEO score

100

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

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 Wellsec.co.nz 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 Wellsec.co.nz 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

wellsec.co.nz

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