3.6 sec in total
37 ms
3 sec
552 ms
Click here to check amazing Scratch content. Otherwise, check out these important facts you probably never knew about scratch.nz
We are a bunch of curious, business-minded problem solvers bent on making web stuff that works | Call us on 09 888 9229.
Visit scratch.nzWe analyzed Scratch.nz page load time and found that the first response time was 37 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
scratch.nz performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.9 s
28/100
25%
Value12.2 s
3/100
10%
Value21,990 ms
0/100
30%
Value0.003
100/100
15%
Value30.5 s
0/100
10%
37 ms
42 ms
18 ms
670 ms
672 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 96% of them (55 requests) were addressed to the original Scratch.nz, 2% (1 request) were made to Cdnjs.cloudflare.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Scratch.nz.
Page size can be reduced by 101.1 kB (45%)
223.8 kB
122.7 kB
In fact, the total size of Scratch.nz main page is 223.8 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. 50% of websites need less resources to load. Javascripts take 112.7 kB which makes up the majority of the site volume.
Potential reduce by 62.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 8.2 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 62.0 kB or 81% of the original size.
Potential reduce by 112 B
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. Scratch images are well optimized though.
Potential reduce by 39.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 39.1 kB or 35% of the original size.
Number of requests can be reduced by 43 (90%)
48
5
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Scratch. 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 12 to 1 for CSS and as a result speed up the page load time.
scratch.nz
37 ms
scratch.nz
42 ms
normalize.min.css
18 ms
cms.css
670 ms
modules.css
672 ms
lightslider.css
26 ms
lightgallery.min.css
674 ms
magnific-popup.css
28 ms
sumoselect.css
26 ms
jquery.mmenu.all.css
39 ms
brand.css
35 ms
layouts.css
42 ms
style.css
51 ms
unite-gallery.css
695 ms
jquery.min.js
40 ms
jquery.json.min.js
51 ms
gravityforms.min.js
59 ms
jquery.sticky.js
60 ms
lightslider.js
742 ms
lightgallery-all.min.js
73 ms
jquery.magnific-popup.js
86 ms
jquery.easytabs.min.js
766 ms
jquery.sumoselect.min.js
674 ms
lazysizes.min.js
679 ms
typed.min.js
684 ms
jquery-match-height.js
1322 ms
jquery.sticky-sidebar.min.js
1325 ms
ResizeSensor.js
740 ms
slidereveal.js
1360 ms
jquery.mmenu.all.js
740 ms
core.js
740 ms
layouts.js
741 ms
unitegallery.min.js
763 ms
ug-theme-tiles.js
764 ms
modules.js
765 ms
js.js
763 ms
dom-ready.min.js
1411 ms
hooks.min.js
1423 ms
i18n.min.js
1420 ms
a11y.min.js
1955 ms
js.js
1318 ms
utils.min.js
1334 ms
vendor-theme.min.js
1972 ms
scripts-theme.min.js
1335 ms
conditional_logic.min.js
1342 ms
lcp-beacon.min.js
1351 ms
gtm.js
100 ms
loading-white.gif
703 ms
device-grey.svg
721 ms
device-blue.svg
1362 ms
sd-icons.ttf
1530 ms
VisbyCF-Regular.woff
1546 ms
VisbyCF-Medium.woff
1551 ms
VisbyCF-DemiBold.woff
2102 ms
VisbyCF-Bold.woff
1701 ms
VisbyCF-ExtraBold.woff
2178 ms
VisbyCF-Heavy.woff
1970 ms
scratch.nz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
scratch.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
scratch.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Scratch.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Scratch.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.
scratch.nz
Open Graph data is detected on the main page of Scratch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: