5 sec in total
834 ms
4.1 sec
135 ms
Visit imagineer.co.jp now to see the best up-to-date Imagineer content for Japan and also check out these interesting facts you probably never knew about imagineer.co.jp
イマジニアは「想像をカタチに変える」をコンセプトとし、コンテンツビジネスを中心に、お客様満足度の高いサービスの提供を目指しています。
Visit imagineer.co.jpWe analyzed Imagineer.co.jp page load time and found that the first response time was 834 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
imagineer.co.jp performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value52.7 s
0/100
25%
Value9.5 s
11/100
10%
Value190 ms
91/100
30%
Value0.381
27/100
15%
Value10.3 s
24/100
10%
834 ms
353 ms
1053 ms
244 ms
218 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that all of those requests were addressed to Imagineer.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Imagineer.co.jp.
Page size can be reduced by 115.9 kB (17%)
669.2 kB
553.3 kB
In fact, the total size of Imagineer.co.jp main page is 669.2 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. Only 10% of websites need less resources to load. Images take 544.9 kB which makes up the majority of the site volume.
Potential reduce by 16.5 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 16.5 kB or 77% of the original size.
Potential reduce by 31.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. Imagineer images are well optimized though.
Potential reduce by 60.0 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 60.0 kB or 64% of the original size.
Potential reduce by 8.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. Imagineer.co.jp needs all CSS files to be minified and compressed as it can save up to 8.4 kB or 86% of the original size.
Number of requests can be reduced by 21 (49%)
43
22
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imagineer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
imagineer.co.jp
834 ms
imastyle.css
353 ms
jquery-1.9.0.min.js
1053 ms
sideline_l.gif
244 ms
logo.gif
218 ms
ekokoku.gif
205 ms
spacer.gif
360 ms
toiawase_1.gif
377 ms
sitemap_1.gif
391 ms
banner_top_sumi.png
1100 ms
bn_energy_imgtop.png
858 ms
bn_top.png
1119 ms
menu_home_1.gif
549 ms
menu_corp_1.gif
561 ms
menu_business_1.gif
580 ms
menu_investor_1.gif
728 ms
menu_news_1.gif
757 ms
menu_recruit_1.gif
779 ms
top_bar.gif
912 ms
dotline_v.gif
954 ms
news.gif
968 ms
smallarrow.gif
1062 ms
top_new_icon_osirase.gif
1088 ms
top_new_icon_service2.gif
1139 ms
top_new_icon_ir2.gif
1158 ms
top_new_icon_irt.gif
1260 ms
more.gif
1271 ms
topic.gif
1274 ms
banner_side_sumi.png
1344 ms
bn_energy.png
1338 ms
opinion.png
1958 ms
ceo_2.gif
1459 ms
privacy.gif
1447 ms
jouken.gif
1453 ms
copyright.gif
1527 ms
sideline_r.gif
1558 ms
toiawase_2.gif
219 ms
sitemap_2.gif
202 ms
menu_home_2.gif
178 ms
menu_corp_2.gif
187 ms
menu_business_2.gif
192 ms
menu_investor_2.gif
185 ms
menu_news_2.gif
353 ms
menu_recruit_2.gif
360 ms
imagineer.co.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.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
imagineer.co.jp 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
imagineer.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 uses legible font sizes
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imagineer.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Imagineer.co.jp 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.
imagineer.co.jp
Open Graph description is not detected on the main page of Imagineer. 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: