5.8 sec in total
555 ms
4.8 sec
468 ms
Click here to check amazing Eyefi content. Otherwise, check out these important facts you probably never knew about eyefi.jp
カメラ趣味ブログ
Visit eyefi.jpWe analyzed Eyefi.jp page load time and found that the first response time was 555 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
eyefi.jp performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value10.7 s
0/100
25%
Value6.8 s
34/100
10%
Value2,210 ms
6/100
30%
Value0.001
100/100
15%
Value12.2 s
15/100
10%
555 ms
357 ms
652 ms
311 ms
481 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Eyefi.jp, 69% (27 requests) were made to Jp.eyefi.com and 5% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Jp.eyefi.com.
Page size can be reduced by 190.6 kB (14%)
1.4 MB
1.2 MB
In fact, the total size of Eyefi.jp main page is 1.4 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. 30% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 18.3 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 18.3 kB or 71% of the original size.
Potential reduce by 83.3 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. Eyefi images are well optimized though.
Potential reduce by 57.8 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 57.8 kB or 58% of the original size.
Potential reduce by 31.1 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. Eyefi.jp needs all CSS files to be minified and compressed as it can save up to 31.1 kB or 82% of the original size.
Number of requests can be reduced by 13 (36%)
36
23
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eyefi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
eyefi.jp
555 ms
eyefi.co.jp
357 ms
jp.eyefi.com
652 ms
MyFontsWebfontsKit.css
311 ms
styles.css
481 ms
jquery.min.js
32 ms
jquery-ui.min.js
53 ms
jcookie.js
335 ms
base.v2.css
378 ms
home.css
73 ms
widget.css
422 ms
quant.js
9 ms
mktFormSupport.js
23 ms
ui.js
320 ms
analytics.js
48 ms
logo.png
310 ms
hero-mobi_pro.jpg
922 ms
mobi_pro.png
752 ms
dgp-s_gold2016.png
304 ms
dgp-s_gold.png
343 ms
tipa.png
672 ms
hero-planned.jpg
1358 ms
camera_card_lockup.png
1087 ms
hero-happen.jpg
1227 ms
mobile_lockup.png
1502 ms
cloud_camera.jpg
1789 ms
cloud_standalone.jpg
1705 ms
devices.jpg
1413 ms
photo_lovers.png
1531 ms
onlinestore.png
1671 ms
2A7050_B_0.woff
2189 ms
2A7050_9_0.woff
2356 ms
pixel;r=1455438322;a=p-b2aClKAJUF696;fpan=1;fpa=P0-1534682651-1458142254779;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458142254778;tzo=-180;ref=;url=http%3A%2F%2Fjp.eyefi.com%2F;ogl=
50 ms
collect
85 ms
sprite_footer_ols_icons.png
1679 ms
munchkin.js
81 ms
munchkin.js
4 ms
visitWebPage
13 ms
mobile.css
320 ms
eyefi.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
eyefi.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
eyefi.jp SEO score
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyefi.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 Eyefi.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.
eyefi.jp
Open Graph description is not detected on the main page of Eyefi. 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: