20.7 sec in total
7.1 sec
13.4 sec
280 ms
Click here to check amazing Two Eyes content. Otherwise, check out these important facts you probably never knew about two-eyes.net
Visit two-eyes.netWe analyzed Two-eyes.net page load time and found that the first response time was 7.1 sec and then it took 13.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
two-eyes.net performance score
name
value
score
weighting
Value1.8 s
90/100
10%
Value1.9 s
98/100
25%
Value6.8 s
35/100
10%
Value660 ms
45/100
30%
Value0
100/100
15%
Value10.1 s
26/100
10%
7078 ms
2990 ms
509 ms
356 ms
1080 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 96% of them (46 requests) were addressed to the original Two-eyes.net, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain Two-eyes.net.
Page size can be reduced by 127.8 kB (61%)
208.4 kB
80.5 kB
In fact, the total size of Two-eyes.net main page is 208.4 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. 20% of websites need less resources to load. Javascripts take 165.9 kB which makes up the majority of the site volume.
Potential reduce by 15.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 15.7 kB or 76% of the original size.
Potential reduce by 1.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. Two Eyes images are well optimized though.
Potential reduce by 106.6 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 106.6 kB or 64% of the original size.
Potential reduce by 4.0 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. Two-eyes.net needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 82% of the original size.
Number of requests can be reduced by 3 (7%)
46
43
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Two Eyes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
two-eyes.net
7078 ms
www.two-eyes.net
2990 ms
index.css
509 ms
indexCOLOR.css
356 ms
jquery.min.js
1080 ms
jquery.bxslider.min.js
768 ms
Index.js
404 ms
indexbody.css
161 ms
back00.png
317 ms
PIC88x31-101-3
331 ms
PIC88x31-101-6
314 ms
PIC88x31-101-7
426 ms
PIC88x31-101-12
311 ms
PIC88x31-101-16
326 ms
PIC88x31-101-17
489 ms
PIC88x31-101-19
494 ms
PIC88x31-101-25
467 ms
PIC88x31-101-26
517 ms
PIC88x31-101-35
523 ms
PIC88x31-101-36
596 ms
PIC88x31-101-37
615 ms
PIC88x31-101-41
665 ms
PIC88x31-101-42
674 ms
PIC88x31-101-45
710 ms
PIC88x31-101-47
715 ms
PIC88x31-101-48
765 ms
PIC88x31-101-49
766 ms
PIC88x31-101-50
842 ms
PIC88x31-101-51
854 ms
PIC88x31-101-52
909 ms
PIC88x31-101-53
911 ms
PIC88x31-101-54
939 ms
PIC88x31-101-55
918 ms
PIC88x31-101-56
1019 ms
PIC88x31-101-57
1033 ms
PIC88x31-101-58
1106 ms
PIC88x31-101-59
1109 ms
PIC88x31-101-60
1072 ms
PIC88x31-101-61
1115 ms
PIC88x31-101-62
1203 ms
PIC88x31-101-63
1214 ms
PIC88x31-101-64
1227 ms
PIC88x31-101-65
1304 ms
IndexTitle
2476 ms
analytics.js
6 ms
collect
12 ms
IndexYES.gif
980 ms
IndexNO.gif
1072 ms
two-eyes.net 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
<frame> or <iframe> elements do not have a title
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
two-eyes.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
two-eyes.net SEO score
N/A
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Two-eyes.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Two-eyes.net main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
two-eyes.net
Open Graph description is not detected on the main page of Two Eyes. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: