1.5 sec in total
198 ms
889 ms
451 ms
Visit native.eco now to see the best up-to-date Native content and also check out these interesting facts you probably never knew about native.eco
Together, we catalyze climate action. Native helps brands achieve Scope 1-3 emissions goals with carbon offsets that positively impact ecosystems and communities most important to your business.
Visit native.ecoWe analyzed Native.eco page load time and found that the first response time was 198 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
native.eco performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value3.8 s
56/100
25%
Value3.6 s
87/100
10%
Value610 ms
49/100
30%
Value0
100/100
15%
Value7.3 s
50/100
10%
198 ms
71 ms
24 ms
32 ms
28 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 97% of them (64 requests) were addressed to the original Native.eco, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to . The less responsive or slowest element that took the longest time to load (284 ms) belongs to the original domain Native.eco.
Page size can be reduced by 304.9 kB (22%)
1.4 MB
1.1 MB
In fact, the total size of Native.eco main page is 1.4 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. 70% of websites need less resources to load. Images take 736.8 kB which makes up the majority of the site volume.
Potential reduce by 187.3 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 187.3 kB or 45% of the original size.
Potential reduce by 84 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. Native images are well optimized though.
Potential reduce by 12.5 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 12.5 kB or 13% of the original size.
Potential reduce by 105.1 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. Native.eco needs all CSS files to be minified and compressed as it can save up to 105.1 kB or 63% of the original size.
Number of requests can be reduced by 23 (37%)
62
39
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Native. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
native.eco
198 ms
native.eco
71 ms
wc-authorize-net-cim-checkout-block.css
24 ms
custom.css
32 ms
swiper-bundle.min.css
28 ms
font-awesome.min.css
155 ms
bootstrap.css
64 ms
jquery.mmenu.all.css
19 ms
the-core-style.css
37 ms
jquery.min.js
34 ms
jquery-migrate.min.js
60 ms
bootstrap.min.js
60 ms
wc-blocks.css
54 ms
wpforms-full.min.css
64 ms
gtm4wp-ecommerce-generic.js
62 ms
gtm4wp-woocommerce.js
63 ms
jquery.customInput.js
62 ms
jquery.mmenu.min.all.js
65 ms
selectize.min.js
64 ms
effect.min.js
65 ms
general.js
66 ms
gtm.js
232 ms
native-logo.png
279 ms
native-logo.png
132 ms
certified.png
130 ms
woman-on-mountain-bg.webp
131 ms
one.webp
134 ms
two.webp
135 ms
three.webp
132 ms
four.webp
132 ms
slider-arrown.svg
138 ms
allbirds-1.png
135 ms
stonyfield-1.png
137 ms
trail-rinning-1.png
228 ms
eileen-fisher-1.png
235 ms
stripe-1.png
229 ms
Xanterra-1.png
229 ms
Ben-jerrys-1.png
229 ms
Bar-clif-1.png
231 ms
Aveda-1.png
230 ms
designtex-1.png
232 ms
Hawkpartners-1.png
234 ms
keurig-1.png
235 ms
everlane-1.png
266 ms
lush-1.png
265 ms
pet-sustainability-1.png
275 ms
REVERB-logo.png
266 ms
permanente-medicine-1.png
267 ms
reunion-1.png
267 ms
partner-re-1.png
267 ms
lime-bike-1.png
270 ms
Planet-upside-down.png
271 ms
Verified-Carbon-Standard.png
269 ms
Gold-Standard-logo.png
272 ms
climate-community-biodiversity-logo.png
274 ms
Plan-Vivo-Logo.webp
276 ms
American-Carbon-Registry-logo.png
284 ms
Verra-Logo.png
217 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
59 ms
fontawesome-webfont.woff
161 ms
Brazil-9-1024x576.jpg
165 ms
location.svg
151 ms
phone.svg
154 ms
Bcorp-logo-1.png
152 ms
search.svg
153 ms
submit-spin.svg
157 ms
native.eco 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
[id] attributes on active, focusable elements are not unique
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
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
native.eco best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
native.eco 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Native.eco 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 Native.eco 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.
native.eco
Open Graph data is detected on the main page of Native. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: