4.2 sec in total
307 ms
3.2 sec
672 ms
Visit wesustain.com now to see the best up-to-date We Sustain content and also check out these interesting facts you probably never knew about wesustain.com
We create flexible software solutions designed to support future-focused, responsible business management – solutions to simplify and streamline your sustainability processes.
Visit wesustain.comWe analyzed Wesustain.com page load time and found that the first response time was 307 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
wesustain.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value19.0 s
0/100
25%
Value12.1 s
4/100
10%
Value4,630 ms
0/100
30%
Value0
100/100
15%
Value22.1 s
1/100
10%
307 ms
49 ms
67 ms
23 ms
40 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wesustain.com, 65% (63 requests) were made to Cority.com and 6% (6 requests) were made to One.cority.com. The less responsive or slowest element that took the longest time to load (573 ms) relates to the external source Munchkin.marketo.net.
Page size can be reduced by 486.9 kB (37%)
1.3 MB
838.9 kB
In fact, the total size of Wesustain.com main page is 1.3 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. 85% 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. Javascripts take 539.2 kB which makes up the majority of the site volume.
Potential reduce by 350.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. 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 350.7 kB or 83% of the original size.
Potential reduce by 0 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. We Sustain images are well optimized though.
Potential reduce by 90.8 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 90.8 kB or 17% of the original size.
Potential reduce by 45.4 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. Wesustain.com needs all CSS files to be minified and compressed as it can save up to 45.4 kB or 20% of the original size.
Number of requests can be reduced by 70 (85%)
82
12
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of We Sustain. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
wesustain.com
307 ms
49 ms
all.min.css
67 ms
premium-addons.min.css
23 ms
style.css
40 ms
flexslider.css
39 ms
glide-core.css
60 ms
style.min.css
60 ms
theme.min.css
61 ms
header-footer.min.css
60 ms
frontend-lite.min.css
62 ms
swiper.min.css
61 ms
frontend-lite.min.css
117 ms
all.min.css
119 ms
v4-shims.min.css
116 ms
style.min.css
114 ms
font-awesome.min.css
126 ms
intlTelInput.min.css
124 ms
app.css
137 ms
style-55247.css
136 ms
dashicons.min.css
134 ms
jquery.min.js
167 ms
jquery-migrate.min.js
135 ms
v4-shims.min.js
166 ms
otSDKStub.js
134 ms
qualified.js
534 ms
forms2.min.js
535 ms
widget-nav-menu.min.css
456 ms
animations.min.css
449 ms
lazysizes.min.js
447 ms
jquery.flexslider-min.js
447 ms
glide-min.js
449 ms
typer.js
448 ms
happy-addons.min.js
449 ms
happy-addons-pro.js
450 ms
intlTelInput.min.js
451 ms
lc.js
449 ms
jquery.smartmenus.min.js
451 ms
helper.min.js
522 ms
webpack-pro.runtime.min.js
520 ms
webpack.runtime.min.js
521 ms
ecd9f026b8.js
449 ms
overlay.js
442 ms
overlay.css
443 ms
frontend-modules.min.js
518 ms
wp-polyfill-inert.min.js
517 ms
regenerator-runtime.min.js
500 ms
wp-polyfill.min.js
505 ms
hooks.min.js
485 ms
i18n.min.js
483 ms
frontend.min.js
484 ms
waypoints.min.js
483 ms
core.min.js
481 ms
frontend.min.js
486 ms
elements-handlers.min.js
432 ms
manifest.js
430 ms
app.js
424 ms
7b9fb221-18db-4587-a2e2-708d84a8ada4.json
349 ms
gtm.js
454 ms
arrow-right-icon.svg
93 ms
product-highlight.jpg
91 ms
white-arrow-right-icon.svg
100 ms
featured-resource.jpg
101 ms
gq-carbon-bg.jpg
102 ms
location
105 ms
FaktPro-Blond.ttf
28 ms
FaktProLight.woff
28 ms
FaktProNormal.woff
29 ms
FaktProMedium.woff
28 ms
FaktProSemiBold.woff
28 ms
FaktProBold.woff
28 ms
FaktProBlack.woff
95 ms
fa-regular-400.woff
101 ms
fa-regular-400.ttf
27 ms
fa-solid-900.woff
187 ms
fa-solid-900.ttf
95 ms
otBannerSdk.js
91 ms
wARDj0u
74 ms
js
120 ms
417 ms
insight.min.js
414 ms
obtp.js
409 ms
bat.js
564 ms
sl.js
526 ms
munchkin.js
573 ms
getForm
354 ms
getForm
315 ms
188 ms
api.min.js
185 ms
forms2.css
92 ms
forms2-theme-simple.css
85 ms
r
58 ms
munchkin.js
31 ms
visitWebPage
120 ms
i
55 ms
zi-tag.js
42 ms
XDFrame
38 ms
wesustain.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
wesustain.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
wesustain.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
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 Wesustain.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 Wesustain.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.
wesustain.com
Open Graph data is detected on the main page of We Sustain. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: