5.7 sec in total
520 ms
3.9 sec
1.2 sec
Click here to check amazing Euglena content for Japan. Otherwise, check out these important facts you probably never knew about euglena.jp
株式会社ユーグレナは、微細藻類ユーグレナ(和名:ミドリムシ)等を活用し食品や化粧品の販売、バイオ燃料の開発・製造を行っているバイオテクノロジー企業です。
Visit euglena.jpWe analyzed Euglena.jp page load time and found that the first response time was 520 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
euglena.jp performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value6.6 s
8/100
25%
Value10.0 s
9/100
10%
Value3,230 ms
2/100
30%
Value0.111
87/100
15%
Value28.2 s
0/100
10%
520 ms
826 ms
19 ms
198 ms
720 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 84% of them (65 requests) were addressed to the original Euglena.jp, 4% (3 requests) were made to Connect.facebook.net and 3% (2 requests) were made to J.wovn.io. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Ssl4.eir-parts.net.
Page size can be reduced by 285.1 kB (6%)
4.9 MB
4.6 MB
In fact, the total size of Euglena.jp main page is 4.9 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 4.5 MB which makes up the majority of the site volume.
Potential reduce by 42.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. This page needs HTML code to be minified as it can gain 9.1 kB, which is 17% 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 42.4 kB or 77% of the original size.
Potential reduce by 51.0 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. Euglena images are well optimized though.
Potential reduce by 144.7 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 144.7 kB or 54% of the original size.
Potential reduce by 47.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. Euglena.jp needs all CSS files to be minified and compressed as it can save up to 47.0 kB or 79% of the original size.
Number of requests can be reduced by 24 (32%)
75
51
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Euglena. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
euglena.jp
520 ms
euglena.jp
826 ms
1
19 ms
common.css
198 ms
parts.css
720 ms
slick.css
751 ms
jquery.js
887 ms
common.js
782 ms
slick.min.js
736 ms
top.css
391 ms
top.js
584 ms
slider.js
786 ms
jquery.cookie.js
906 ms
cookieConsent.js
985 ms
widget
6 ms
3L7xFp
183 ms
gtm.js
148 ms
cf28c07382c2b212cfc292572a2a5c96.jpg
216 ms
header_logo.svg
366 ms
production.jpg
143 ms
genkireport.jpg
131 ms
project_s.jpg
175 ms
news.jpg
88 ms
business_hc1.jpg
138 ms
business_hc5.jpg
139 ms
business_hc2.jpg
331 ms
business_hc3.jpg
335 ms
business_hc7.jpg
330 ms
business_hc4.jpg
332 ms
business_hc6.jpg
334 ms
business_hc9.jpg
339 ms
business_hc8.jpg
339 ms
biofuel1.jpg
352 ms
biofuel2.jpg
365 ms
biofuel3.jpg
354 ms
social1.jpg
346 ms
social2.jpg
347 ms
other1.jpg
354 ms
project_no51.jpg
357 ms
project3.jpg
373 ms
project1.jpg
379 ms
contact_pc.png
360 ms
recruit_pc.png
364 ms
onlineshop_pc.png
371 ms
stimes_pc.png
370 ms
myhealth_pc.png
387 ms
eairport_pc.png
373 ms
footerlogo.png
377 ms
photo_image.jpg
230 ms
2312_image-photo_9.jpg
246 ms
tag.js
137 ms
cmt.js
638 ms
one_tag2.js
727 ms
fbevents.js
136 ms
sdk.js
169 ms
blank_w.svg
563 ms
img_up.png
567 ms
main_ttl_pc.svg
530 ms
img_down.png
578 ms
bgimg1_pc.svg
544 ms
sbt_ep_pc.png
500 ms
arw.svg
667 ms
announcement_10.js
1551 ms
sbt_healthcare_pc.png
643 ms
blank_b.svg
640 ms
blank_p.svg
652 ms
sbt_biofuel_pc.png
638 ms
sdk.js
5 ms
31 ms
sbt_social_pc.png
619 ms
sbt_other_pc.png
638 ms
time.png
457 ms
pagetop.png
661 ms
sns_x.png
466 ms
sns_fb.png
472 ms
sns_yt.png
480 ms
sustain.svg
649 ms
euglena.jp 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
Links do not have a discernible name
euglena.jp 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
Missing source maps for large first-party JavaScript
euglena.jp 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 Euglena.jp 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 Euglena.jp 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.
euglena.jp
Open Graph data is detected on the main page of Euglena. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: