7.9 sec in total
1.7 sec
5.2 sec
978 ms
Visit nonnative.com now to see the best up-to-date Nonnative content for United States and also check out these interesting facts you probably never knew about nonnative.com
洋服とは、人生を投影するための道具である。nonnative(ノンネイティブ)は、そんな普遍的なアーカイヴ(道具)の中から、用途に合った生地・丈夫な縫製・実用的なディテールといった「機能」を抽出。時流にあったシルエットに再編集する。都市生活のみならず、様々な場所やシチュエーションに適応する東京発の新スタンダード。
Visit nonnative.comWe analyzed Nonnative.com page load time and found that the first response time was 1.7 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
nonnative.com performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value18.7 s
0/100
25%
Value13.8 s
1/100
10%
Value30 ms
100/100
30%
Value0.066
97/100
15%
Value4.7 s
80/100
10%
1742 ms
236 ms
687 ms
511 ms
345 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 85% of them (96 requests) were addressed to the original Nonnative.com, 4% (4 requests) were made to F.vimeocdn.com and 3% (3 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Nonnative.com.
Page size can be reduced by 889.9 kB (14%)
6.5 MB
5.6 MB
In fact, the total size of Nonnative.com main page is 6.5 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. 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 5.4 MB which makes up the majority of the site volume.
Potential reduce by 65.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 10.3 kB, which is 13% 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 65.0 kB or 85% of the original size.
Potential reduce by 84.6 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. Nonnative images are well optimized though.
Potential reduce by 450.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 450.8 kB or 66% of the original size.
Potential reduce by 289.5 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. Nonnative.com needs all CSS files to be minified and compressed as it can save up to 289.5 kB or 86% of the original size.
Number of requests can be reduced by 27 (25%)
108
81
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nonnative. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
nonnative.com
1742 ms
naf2hhh.js
236 ms
bootstrap.min.css
687 ms
style.css
511 ms
responsive.css
345 ms
animate.css
367 ms
featherlight.min.css
366 ms
font-awesome.min.css
516 ms
css
26 ms
css
38 ms
styles.css
381 ms
jquery.js
750 ms
jquery-migrate.min.js
513 ms
nonnative.com
93 ms
wp-emoji-release.min.js
183 ms
jquery.form.min.js
175 ms
scripts.js
176 ms
wp-embed.min.js
185 ms
jquery.js
517 ms
featherlight.min.js
365 ms
bootstrap.min.js
365 ms
jquery.vide.min.js
365 ms
jquery.easing.min.js
367 ms
wow.min.js
398 ms
grayscale.js
547 ms
155773126
111 ms
nonnative_logo.png
301 ms
non16ss.jpg
709 ms
grid.png
693 ms
pl_01.jpg
882 ms
01.jpg
823 ms
bg_style.jpg
695 ms
02.jpg
969 ms
03.jpg
1034 ms
04.jpg
967 ms
05.jpg
869 ms
06.jpg
1167 ms
07.jpg
1047 ms
08.jpg
1068 ms
09.jpg
1304 ms
10.jpg
1310 ms
11.jpg
1401 ms
12.jpg
1227 ms
13.jpg
1258 ms
14.jpg
1509 ms
15.jpg
1409 ms
16.jpg
1443 ms
17.jpg
1645 ms
18.jpg
1494 ms
19.jpg
1765 ms
20.jpg
1595 ms
21.jpg
1631 ms
22.jpg
1667 ms
23.jpg
1851 ms
bg_white.jpg
1728 ms
-NkoGegKUR1RwPJqZfgyxbYsP7INGJX8d99KSl4EYIqffO5FgsMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
37 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
4 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
12 ms
player.js
104 ms
player.css
91 ms
ga.js
31 ms
vuid.min.js
104 ms
fontawesome-webfont.woff
1702 ms
bd_store_top.gif
1700 ms
product.jpg
1734 ms
j.jpg
1835 ms
__utm.gif
29 ms
v.jpg
1813 ms
proxy.html
24 ms
s.jpg
1695 ms
k.jpg
1710 ms
ga.js
391 ms
p.gif
121 ms
c.jpg
1339 ms
t.jpg
1339 ms
p.jpg
1437 ms
__utm.gif
11 ms
h.jpg
1428 ms
a.jpg
1344 ms
bl.jpg
1321 ms
bg.jpg
1321 ms
so.jpg
1238 ms
f.jpg
1360 ms
top_bg.jpg
1296 ms
bd_store.gif
1290 ms
bd_place.gif
1310 ms
top_bg_un.jpg
1211 ms
bg_run2.jpg
1329 ms
23.jpg
1253 ms
22.jpg
1207 ms
21.jpg
1199 ms
20.jpg
1152 ms
19.jpg
1150 ms
18.jpg
1237 ms
17.jpg
1191 ms
16.jpg
1188 ms
15.jpg
1128 ms
14.jpg
1096 ms
13.jpg
1098 ms
12.jpg
1182 ms
11.jpg
1098 ms
10.jpg
1101 ms
9.jpg
1081 ms
8.jpg
1066 ms
7.jpg
1075 ms
6.jpg
1170 ms
5.jpg
1088 ms
4.jpg
1101 ms
3.jpg
1076 ms
2.jpg
1063 ms
1.jpg
1086 ms
bg_arc.jpg
1171 ms
ajax-loader.gif
1077 ms
nonnative.com 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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Definition list items are not wrapped in <dl> elements
List items (<li>) are not contained within <ul> or <ol> parent elements.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
nonnative.com 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
General
Impact
Issue
Detected JavaScript libraries
nonnative.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 doesn't use legible font sizes
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nonnative.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Nonnative.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.
nonnative.com
Open Graph data is detected on the main page of Nonnative. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: