Tools & Wizards About Us
customscreensnz.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

customscreensnz.com

Custom Screens LTD

Page Load Speed

7.2 sec in total

First Response

1.7 sec

Resources Loaded

4.5 sec

Page Rendered

922 ms

customscreensnz.com screenshot

About Website

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

Visit customscreensnz.com

Key Findings

We analyzed Customscreensnz.com page load time and found that the first response time was 1.7 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

customscreensnz.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value2,480 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value23.9 s

1/100

10%

Network Requests Diagram

customscreensnz.com

1715 ms

theplus-post-8.min.css

99 ms

iconsmind.min.css

206 ms

plus-pre-loader.min.css

214 ms

all.min.css

280 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 215.4 kB (10%)

Content Size

2.1 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Customscreensnz.com main page is 2.1 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. 65% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 114.7 kB

  • Original 136.2 kB
  • After minification 131.7 kB
  • After compression 21.5 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 114.7 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 1.4 kB

  • Original 1.4 MB
  • After minification 1.4 MB

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. Custom Screens Nz images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 17.8 kB

  • Original 317.5 kB
  • After minification 317.5 kB
  • After compression 299.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.

CSS Optimization

-36%

Potential reduce by 81.4 kB

  • Original 223.6 kB
  • After minification 223.6 kB
  • After compression 142.2 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. Customscreensnz.com needs all CSS files to be minified and compressed as it can save up to 81.4 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (74%)

Requests Now

78

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

customscreensnz.com

customscreensnz.com

1715 ms

theplus-post-8.min.css

theplus-post-8.min.css

99 ms

iconsmind.min.css

iconsmind.min.css

206 ms

plus-pre-loader.min.css

plus-pre-loader.min.css

214 ms

all.min.css

all.min.css

280 ms

simple-line-icons.min.css

simple-line-icons.min.css

232 ms

style.min.css

style.min.css

293 ms

elementor-icons.min.css

elementor-icons.min.css

230 ms

frontend-lite.min.css

frontend-lite.min.css

302 ms

swiper.min.css

swiper.min.css

306 ms

post-30.css

post-30.css

322 ms

frontend-lite.min.css

frontend-lite.min.css

328 ms

global.css

global.css

364 ms

post-8.css

post-8.css

393 ms

post-38.css

post-38.css

392 ms

post-41.css

post-41.css

396 ms

style.css

style.css

409 ms

css

css

38 ms

fontawesome.min.css

fontawesome.min.css

418 ms

solid.min.css

solid.min.css

447 ms

brands.min.css

brands.min.css

488 ms

jquery.min.js

jquery.min.js

503 ms

jquery-migrate.min.js

jquery-migrate.min.js

483 ms

plus-pre-loader-extra-transition.min.js

plus-pre-loader-extra-transition.min.js

519 ms

plus-pre-loader.min.js

plus-pre-loader.min.js

502 ms

js

js

76 ms

widget-icon-list.min.css

widget-icon-list.min.css

551 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

580 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

583 ms

widget-icon-box.min.css

widget-icon-box.min.css

603 ms

widget-carousel.min.css

widget-carousel.min.css

603 ms

post-66.css

post-66.css

592 ms

e-gallery.min.css

e-gallery.min.css

630 ms

core.min.js

core.min.js

708 ms

mouse.min.js

mouse.min.js

709 ms

slider.min.js

slider.min.js

712 ms

theplus-post-8.min.js

theplus-post-8.min.js

716 ms

draggable.min.js

draggable.min.js

712 ms

jquery.ui.touch-punch.js

jquery.ui.touch-punch.js

718 ms

imagesloaded.min.js

imagesloaded.min.js

686 ms

theme.min.js

theme.min.js

586 ms

drop-down-mobile-menu.min.js

drop-down-mobile-menu.min.js

613 ms

drop-down-search.min.js

drop-down-search.min.js

599 ms

magnific-popup.min.js

magnific-popup.min.js

598 ms

ow-lightbox.min.js

ow-lightbox.min.js

550 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

579 ms

ow-slider.min.js

ow-slider.min.js

581 ms

scroll-effect.min.js

scroll-effect.min.js

594 ms

scroll-top.min.js

scroll-top.min.js

581 ms

select.min.js

select.min.js

580 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

558 ms

e-gallery.min.js

e-gallery.min.js

585 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

600 ms

webpack.runtime.min.js

webpack.runtime.min.js

603 ms

frontend-modules.min.js

frontend-modules.min.js

612 ms

hooks.min.js

hooks.min.js

589 ms

i18n.min.js

i18n.min.js

577 ms

frontend.min.js

frontend.min.js

963 ms

waypoints.min.js

waypoints.min.js

610 ms

frontend.min.js

frontend.min.js

614 ms

elements-handlers.min.js

elements-handlers.min.js

1004 ms

hedr-bck.jpg

hedr-bck.jpg

1704 ms

fa-brands-400.woff

fa-brands-400.woff

914 ms

fa-brands-400.ttf

fa-brands-400.ttf

1028 ms

header-logo.png

header-logo.png

1243 ms

bnr-img-1.png

bnr-img-1.png

1820 ms

abt-img.png

abt-img.png

1337 ms

sec3-img-1.png

sec3-img-1.png

1402 ms

dividerr.png

dividerr.png

973 ms

icn-1.jpg

icn-1.jpg

1066 ms

icn-2.jpg

icn-2.jpg

1142 ms

icn-3.jpg

icn-3.jpg

1189 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

19 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

32 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

53 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

69 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

68 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

70 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

70 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

71 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

69 ms

fa-solid-900.woff

fa-solid-900.woff

1463 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

70 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYA.ttf

71 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

73 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf

72 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

73 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

73 ms

fa-solid-900.ttf

fa-solid-900.ttf

1489 ms

fa-regular-400.ttf

fa-regular-400.ttf

1300 ms

clnt-1.png

clnt-1.png

1303 ms

clnt-2.png

clnt-2.png

1274 ms

footer-logo.png

footer-logo.png

1371 ms

f-gl-1.png

f-gl-1.png

1346 ms

f-gl-2.png

f-gl-2.png

1446 ms

f-gl-3.png

f-gl-3.png

1446 ms

f-gl-4.png

f-gl-4.png

1390 ms

f-gl-5.png

f-gl-5.png

1411 ms

f-gl-6.png

f-gl-6.png

1448 ms

Accessibility Review

customscreensnz.com accessibility score

95

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

customscreensnz.com best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

customscreensnz.com SEO score

85

Search Engine Optimization Advices

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

customscreensnz.com

Open Graph description is not detected on the main page of Custom Screens Nz. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: