5.1 sec in total
527 ms
4.3 sec
276 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 527 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
imagineer.co.jp performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value60.2 s
0/100
25%
Value12.1 s
3/100
10%
Value210 ms
89/100
30%
Value0.375
28/100
15%
Value12.5 s
14/100
10%
527 ms
1025 ms
666 ms
690 ms
716 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 91% of them (53 requests) were addressed to the original Imagineer.co.jp, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Imagineer.co.jp.
Page size can be reduced by 903.1 kB (7%)
13.0 MB
12.1 MB
In fact, the total size of Imagineer.co.jp main page is 13.0 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. 55% of websites need less resources to load. Images take 12.7 MB which makes up the majority of the site volume.
Potential reduce by 42.2 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 6.1 kB, which is 12% 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.2 kB or 86% of the original size.
Potential reduce by 710.9 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 122.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 122.0 kB or 65% of the original size.
Potential reduce by 27.9 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 27.9 kB or 82% of the original size.
Number of requests can be reduced by 10 (18%)
56
46
The browser has sent 56 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 from 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
imagineer.co.jp
527 ms
imagineer.co.jp
1025 ms
jquery-2.1.1.min.js
666 ms
jquery.fs.zoomer.js
690 ms
common.css
716 ms
site_top.js
694 ms
owl.carousel.min.js
868 ms
jquery.fs.zoomer.css
723 ms
site_top.css
832 ms
owl.carousel.min.css
861 ms
owl.theme.default.min.css
865 ms
js
60 ms
top_logo.png
176 ms
menu.png
179 ms
totop.png
177 ms
M1.png
1034 ms
M8.png
1033 ms
M3.png
1076 ms
M2.png
848 ms
M7.png
1034 ms
M4.png
1249 ms
font2.png
1017 ms
font1.png
1185 ms
pdf.gif
1205 ms
to.png
1205 ms
slide_fit_miku.png
1206 ms
slide_kanken.png
1254 ms
slide_eiken.png
1352 ms
slide_opi.png
1377 ms
slide_fit_dance.png
1378 ms
slide_medarot.png
1380 ms
slide_boxing2.png
1427 ms
slide_hokuto.jpg
1435 ms
slide_coloringbook.png
1519 ms
slide_sfarm.png
1551 ms
slide_puppy.png
1553 ms
slide_comic.png
1555 ms
slide_fit_miku_l.png
1608 ms
slide_kanken_l.png
1615 ms
slide_eiken_l.png
1687 ms
slide_opi_l.png
1724 ms
slide_fit_dance_l.png
1726 ms
slide_medarot_l.png
1727 ms
slide_boxing2_l.png
1787 ms
slide_hokuto_l.jpg
1796 ms
slide_coloringbook_l.png
1854 ms
slide_sfarm_l.png
1896 ms
slide_puppy_l.png
1866 ms
js
41 ms
analytics.js
4 ms
collect
15 ms
slide_comic_l.png
1728 ms
infoc.png
1793 ms
infoir.png
1800 ms
collect
28 ms
infobiz.png
1176 ms
inforecruit.png
1056 ms
maru.png
1042 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
JA
UTF-8
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 it matches the claimed language. Our system also found out that Imagineer.co.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.
imagineer.co.jp
Open Graph data is detected on the main page of Imagineer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: