5.8 sec in total
526 ms
4.2 sec
1.1 sec
Click here to check amazing Evergreendaze content. Otherwise, check out these important facts you probably never knew about evergreendaze.com
実際の結婚相談所参加の記録を写真と動画で一覧比較できるようにしました!パーティーの様子などを知りたい方はぜひ見てくださいね!
Visit evergreendaze.comWe analyzed Evergreendaze.com page load time and found that the first response time was 526 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
evergreendaze.com performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value0
0/100
25%
Value15.4 s
1/100
10%
Value6,630 ms
0/100
30%
Value0.216
58/100
15%
Value40.5 s
0/100
10%
526 ms
723 ms
403 ms
398 ms
397 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 53% of them (26 requests) were addressed to the original Evergreendaze.com, 10% (5 requests) were made to Youtube.com and 8% (4 requests) were made to Www11.a8.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Evergreendaze.com.
Page size can be reduced by 404.5 kB (46%)
876.0 kB
471.5 kB
In fact, the total size of Evergreendaze.com main page is 876.0 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. 65% of websites need less resources to load. Images take 364.2 kB which makes up the majority of the site volume.
Potential reduce by 14.4 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 14.4 kB or 66% of the original size.
Potential reduce by 22.8 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. Evergreendaze images are well optimized though.
Potential reduce by 137.9 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 137.9 kB or 65% of the original size.
Potential reduce by 229.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. Evergreendaze.com needs all CSS files to be minified and compressed as it can save up to 229.4 kB or 83% of the original size.
Number of requests can be reduced by 19 (42%)
45
26
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Evergreendaze. 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 from 4 to 1 for CSS and as a result speed up the page load time.
evergreendaze.com
526 ms
www.evergreendaze.com
723 ms
styles.css
403 ms
0.gif
398 ms
0.gif
397 ms
0.gif
396 ms
hg103_72a.jpg
561 ms
2014y01m25d_191245035.jpg
717 ms
2014y01m25d_191512189.jpg
888 ms
2014y01m25d_191714107.jpg
745 ms
0ekj48zq7bblpzc.jpg
899 ms
2014y01m25d_192000110.jpg
1062 ms
2014y01m25d_192132630.jpg
1191 ms
0.gif
393 ms
0.gif
393 ms
cjWhzUkz_zY
91 ms
S4yKD2gFcqU
74 ms
wqbGoAE2U00
63 ms
www-embed-player-vflfNyN_r.css
30 ms
www-embed-player.js
59 ms
base.js
97 ms
0.gif
591 ms
rOtKIt48L-I
225 ms
0.gif
878 ms
0.gif
438 ms
0.gif
396 ms
0.gif
398 ms
2014y02m06d_105121242.jpg
1173 ms
img11_5.jpg
1229 ms
2014y02m06d_110912268.jpg
1378 ms
2015y06m02d_191027278.jpg
1235 ms
2015y06m02d_191557157.jpg
1362 ms
2015y06m02d_192524841.jpg
1652 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
115 ms
ad_status.js
103 ms
bjTRKofZJiU
156 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
75 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
74 ms
tables.css
1284 ms
commonstyles.css
1339 ms
null_image.gif
8 ms
cnt_bg.png
182 ms
header.jpg
1416 ms
dec1_body.gif
373 ms
decbox1.gif
514 ms
rank1_a.gif
378 ms
rank2_a.gif
406 ms
rank3_a.gif
502 ms
footer.gif
694 ms
evergreendaze.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
<frame> or <iframe> elements do not have a title
evergreendaze.com 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
Browser errors were logged to the console
Page has valid source maps
evergreendaze.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
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
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Evergreendaze.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 Evergreendaze.com 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.
evergreendaze.com
Open Graph description is not detected on the main page of Evergreendaze. 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: