6.6 sec in total
624 ms
5.6 sec
422 ms
Click here to check amazing WEG content. Otherwise, check out these important facts you probably never knew about weg.co.nz
Discover the solution you need TRind is a wholly New Zealand owned and operated company providing engineering excellence and first rate customer support for sizing and supply of WEG electric motors, ...
Visit weg.co.nzWe analyzed Weg.co.nz page load time and found that the first response time was 624 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
weg.co.nz performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value22.3 s
0/100
25%
Value25.8 s
0/100
10%
Value33,330 ms
0/100
30%
Value0.074
95/100
15%
Value47.9 s
0/100
10%
624 ms
955 ms
1090 ms
68 ms
73 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Weg.co.nz, 80% (60 requests) were made to Trind.co.nz and 8% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Trind.co.nz.
Page size can be reduced by 224.8 kB (37%)
605.9 kB
381.2 kB
In fact, the total size of Weg.co.nz main page is 605.9 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. Images take 332.4 kB which makes up the majority of the site volume.
Potential reduce by 214.2 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 214.2 kB or 85% of the original size.
Potential reduce by 10.5 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. WEG images are well optimized though.
Potential reduce by 101 B
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.
Number of requests can be reduced by 47 (72%)
65
18
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WEG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
weg.co.nz
624 ms
trind.co.nz
955 ms
trind.co.nz
1090 ms
wp-emoji-release.min.js
68 ms
style.min.css
73 ms
wc-blocks-vendors-style.css
80 ms
wc-blocks-style.css
176 ms
styles.css
213 ms
lightbox.min.css
102 ms
style.css
124 ms
mods.css
106 ms
css
77 ms
style.css
188 ms
font-awesome.css
188 ms
ilightbox.css
192 ms
animations.css
204 ms
woocommerce.css
198 ms
main-frontend.css
197 ms
main-frontend.css
200 ms
frontend.css
225 ms
frontend.css
202 ms
frontend.css
216 ms
frontend.css
213 ms
jquery-1.12.4-wp.js
235 ms
jquery-migrate-1.4.1-wp.js
257 ms
rbtools.min.js
261 ms
rs6.min.js
310 ms
mods.js
259 ms
js
69 ms
frontend.js
864 ms
frontend.js
256 ms
frontend.js
309 ms
frontend.js
310 ms
css
44 ms
rs6.css
51 ms
index.js
49 ms
index.js
48 ms
jquery.blockUI.min.js
47 ms
add-to-cart.min.js
47 ms
js.cookie.min.js
104 ms
woocommerce.min.js
78 ms
cart-fragments.min.js
71 ms
wp-lightbox-2.min.js
105 ms
comment-reply.min.js
106 ms
main.min.js
170 ms
api.js
103 ms
regenerator-runtime.min.js
163 ms
wp-polyfill.min.js
163 ms
index.js
164 ms
analytics.js
53 ms
js
78 ms
collect
68 ms
logo.png
70 ms
logo@2x.png
73 ms
logo-ftr.png
70 ms
logo-ftr@2x.png
71 ms
dummy.png
72 ms
ultimate_design_logo.png
684 ms
jizaRExUiTo99u79D0KEwA.ttf
70 ms
jizfRExUiTo99u79B_mh0O6tKA.ttf
196 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
196 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
198 ms
icomoon.woff
631 ms
bWt97fPFfRzkCa9Jlp6IacVcWQ.ttf
130 ms
recaptcha__en.js
305 ms
trind.co.nz
1717 ms
sign-up-bg-blue.jpg
201 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
76 ms
weg-logo-hdr.png
108 ms
motors-icon.png
485 ms
controls-icon.png
73 ms
automation-icon.png
61 ms
service-icon.png
256 ms
logo-ftr.png
55 ms
sign-up-bg-blue-2.jpg
1277 ms
weg.co.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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
weg.co.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
weg.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weg.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 Weg.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.
weg.co.nz
Open Graph data is detected on the main page of WEG. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: