9 sec in total
1.7 sec
6.9 sec
390 ms
Visit eggstar.info now to see the best up-to-date Eggstar content for Japan and also check out these interesting facts you probably never knew about eggstar.info
東京都渋谷区の芸能プロダクションであるエッグスターのコーポレートサイトです。所属タレントのプロフィールや最新のオーディション情報などを紹介しております。随時所属タレントを募集しておりますので詳しくはオーディションページより
Visit eggstar.infoWe analyzed Eggstar.info page load time and found that the first response time was 1.7 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
eggstar.info performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value30.3 s
0/100
25%
Value21.9 s
0/100
10%
Value750 ms
39/100
30%
Value2.016
0/100
15%
Value24.0 s
1/100
10%
1692 ms
335 ms
15 ms
358 ms
377 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 30% of them (31 requests) were addressed to the original Eggstar.info, 25% (25 requests) were made to Static.xx.fbcdn.net and 19% (19 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Eggstar.info.
Page size can be reduced by 682.6 kB (18%)
3.8 MB
3.1 MB
In fact, the total size of Eggstar.info main page is 3.8 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 17.6 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 3.4 kB, which is 15% 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 17.6 kB or 80% of the original size.
Potential reduce by 159.2 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. Eggstar images are well optimized though.
Potential reduce by 259.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 259.5 kB or 59% of the original size.
Potential reduce by 246.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. Eggstar.info needs all CSS files to be minified and compressed as it can save up to 246.4 kB or 83% of the original size.
Number of requests can be reduced by 50 (52%)
97
47
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eggstar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.eggstar.info
1692 ms
style.css
335 ms
conversion.js
15 ms
styles.css
358 ms
slideshow.min.css
377 ms
mappress.css
567 ms
jquery.js
1006 ms
jquery-migrate.min.js
399 ms
slideshow.min.js
497 ms
jquery.form.min.js
516 ms
scripts.js
368 ms
scroll.js
402 ms
layout.css
532 ms
44 ms
body_sub_bg.png
1378 ms
site_id.png
566 ms
facebook.png
234 ms
privacy-policy.png
226 ms
sitemap.png
234 ms
top_image02.png
571 ms
image4.jpg
1233 ms
top_image03.png
2035 ms
top_image01.jpg
1866 ms
eggstar-audition-hp.jpg
907 ms
top_kids_audition.jpg
2585 ms
Attachment-1.jpeg
1863 ms
ttl_news.png
1464 ms
btn_linklist.png
1485 ms
37 ms
43 ms
31 ms
analytics.js
20 ms
z7VFq7x18dw
137 ms
fzk2KKMpU14
148 ms
ZEqJPmfWUwI
232 ms
gnav.png
1425 ms
loading.gif
1512 ms
arrow_02.png
1591 ms
footer_arrow.png
1690 ms
ga.js
24 ms
collect
59 ms
body_bg.png
2376 ms
__utm.gif
23 ms
www-embed-player-vflfNyN_r.css
28 ms
www-embed-player.js
48 ms
base.js
107 ms
likebox.php
480 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
70 ms
ad_status.js
76 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
131 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
131 ms
kyEKgjk51ZE.css
182 ms
xgj7bXhJNEH.css
223 ms
Czh0gDTFcBt.css
263 ms
N-k91nHCZS2.css
340 ms
ZeuPykSxSED.css
344 ms
f3zkXvjB9aD.css
309 ms
XUOUvx124Lk.css
304 ms
q68gy-v_YMF.js
344 ms
FJmpeSpHpjS.js
384 ms
0wM5s1Khldu.js
367 ms
1bNoFZUdlYZ.js
368 ms
njO1TPvGzoR.js
384 ms
1QuX41zDRrx.js
398 ms
Oagsvfb4VWi.js
421 ms
LTv6ZK-5zxz.js
502 ms
1FCa-btixu2.js
425 ms
DVtj8v6ogQI.js
424 ms
IjqSyiwKeaX.js
423 ms
n6VgtouijQL.js
425 ms
1604721_256116567923538_8854631178303050520_n.png
394 ms
safe_image.php
277 ms
safe_image.php
1969 ms
safe_image.php
423 ms
safe_image.php
461 ms
safe_image.php
2239 ms
safe_image.php
2373 ms
10313951_256115624590299_1631939787068490524_n.png
582 ms
11203690_739913576143551_5715692441691935208_n.jpg
532 ms
392110_107923799325429_2013762332_n.jpg
502 ms
11903700_884301918285897_7892250385693532927_n.jpg
500 ms
12728886_188232078199909_216660480399447201_n.jpg
502 ms
12688334_217398155277046_3358510103232159363_n.jpg
503 ms
12038450_820678331385361_6501553798172243161_n.jpg
594 ms
12472548_1884869845072695_6360428819675732636_n.jpg
574 ms
12191837_135602910129794_8741541089079797461_n.jpg
608 ms
10505596_694400140706528_4577534673726668794_n.jpg
590 ms
10806447_1674811229411977_315250034700968277_n.jpg
748 ms
12295312_947755678645544_1865778864843226535_n.jpg
787 ms
12342803_915507771858618_7114111048541264040_n.jpg
620 ms
10413395_117568061914728_4883469527319030820_n.jpg
681 ms
10313951_256115624590299_1631939787068490524_n.png
826 ms
12715642_512037235664802_2332653640195042421_n.jpg
796 ms
10437463_512037262331466_1217238674144061014_n.jpg
770 ms
12733468_509867805881745_3538940840688500949_n.jpg
851 ms
wL6VQj7Ab77.png
63 ms
s7jcwEQH7Sx.png
64 ms
QDwYpIaRyfG.png
63 ms
K00K-UgnsKu.png
60 ms
108 ms
I6-MnjEovm5.js
41 ms
pQrUxxo5oQp.js
81 ms
eggstar.info 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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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
Links do not have a discernible name
eggstar.info 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
Page has valid source maps
eggstar.info 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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eggstar.info can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Eggstar.info 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.
eggstar.info
Open Graph data is detected on the main page of Eggstar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: