5.7 sec in total
1.2 sec
4.1 sec
333 ms
Click here to check amazing AFFLUX content. Otherwise, check out these important facts you probably never knew about afflux.jp
AFFLUX(アフラックス)は、約180種類の婚約指輪、結婚指輪をオーダーメイドで提案する日本のブライダルジュエリーブランドです。おふたりの想いを大切に指輪に込めて身に着けて頂けるように親切丁寧なご説明と一生涯のアフターメンテナンスを全国80店舗で対応します。
Visit afflux.jpWe analyzed Afflux.jp page load time and found that the first response time was 1.2 sec 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.
afflux.jp performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value20.3 s
0/100
25%
Value10.7 s
7/100
10%
Value1,100 ms
23/100
30%
Value0.57
12/100
15%
Value15.0 s
7/100
10%
1241 ms
86 ms
58 ms
267 ms
412 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 73% of them (66 requests) were addressed to the original Afflux.jp, 11% (10 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Afflux.jp.
Page size can be reduced by 153.2 kB (9%)
1.6 MB
1.5 MB
In fact, the total size of Afflux.jp main page is 1.6 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 123.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. 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 123.4 kB or 68% of the original size.
Potential reduce by 20.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. AFFLUX images are well optimized though.
Potential reduce by 62 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 9.8 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. Afflux.jp needs all CSS files to be minified and compressed as it can save up to 9.8 kB or 19% of the original size.
Number of requests can be reduced by 56 (71%)
79
23
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AFFLUX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
afflux.jp
1241 ms
gtm.js
86 ms
analytics.js
58 ms
wp-emoji-release.min.js
267 ms
wpfp.css
412 ms
style.css
429 ms
wp-customer-reviews.css
447 ms
style.min.css
591 ms
select.css
445 ms
screen.min.css
447 ms
blocks.css
556 ms
jquery.min.js
710 ms
jquery-migrate.min.js
593 ms
wp-customer-reviews.js
597 ms
script.js
597 ms
all.css
74 ms
css2
46 ms
css
75 ms
css2
76 ms
css2
77 ms
slick-theme.css
701 ms
slick.css
735 ms
animate.css
735 ms
reset.css
741 ms
common-renew.css
742 ms
templete.css
847 ms
home-top.css
849 ms
jquery.bxslider.min.css
880 ms
jquery.1.8.2.min.js
1028 ms
jquery.bxslider.min.js
886 ms
jquery.tile.js
886 ms
wow.min.js
994 ms
templete-new.js
990 ms
slick.min.js
1025 ms
platform.js
39 ms
select.js
1030 ms
front.min.js
1030 ms
postviews-cache.js
1129 ms
global.js
1138 ms
jquery.scrollTo.js
1170 ms
js
43 ms
fonts.css
733 ms
sdk.js
126 ms
logo.svg
202 ms
reserve_i.svg
201 ms
favorite_i.svg
193 ms
m_engagement_img.png
194 ms
m_marriage_img.png
338 ms
m_setring_img.png
200 ms
m_fb_i.svg
349 ms
m_tw_i.svg
357 ms
m_insta_i.svg
363 ms
m_yt_i.svg
364 ms
ft_shop_btn.svg
363 ms
ft_favorite_btn.svg
506 ms
ft_tel_btn.svg
507 ms
pc_01-01.jpg
944 ms
sp_01-01.jpg
954 ms
%E3%83%96%E3%83%A9%E3%82%A4%E3%83%80%E3%83%AB%E3%83%AA%E3%83%B3%E3%82%B0.jpg
660 ms
Zoe.jpg
658 ms
LABPINK.jpg
778 ms
TimelessPeople.jpg
776 ms
%E3%83%9E%E3%83%AA%E3%83%83%E3%82%B8%E3%83%AA%E3%83%B3%E3%82%B0%E3%83%A9%E3%83%9C%E3%83%A9%E3%83%88%E3%83%AA%E3%83%BC.jpg
804 ms
YASUEI.jpg
804 ms
%E3%83%AA%E3%83%95%E3%82%A9%E3%83%BC%E3%83%A0%E3%82%B8%E3%83%A5%E3%82%A8%E3%83%AA%E3%83%BC.jpg
1057 ms
reserve_img_pc.jpg
923 ms
reserve_img_sp.jpg
950 ms
shop_img.jpg
951 ms
tryingon_i.svg
1069 ms
support_i.svg
1088 ms
cata_i.svg
1095 ms
f_fb_i.svg
1097 ms
f_tw_i.svg
1097 ms
f_insta_i.svg
1196 ms
f_yt_i.svg
1214 ms
ajax-loader.gif
1198 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf
356 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf
381 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf
560 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf
380 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf
433 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75s.ttf
410 ms
widgets.js
145 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RUAw.ttf
420 ms
xn76YHIn1mWmVKl8ZtAM9NrJfN5GJW41.ttf
382 ms
xn76YHIn1mWmVKl8ZtAM9NrJfN4YJW41.ttf
382 ms
8QIRdiDaitzr7brc8ahpxt6GcIJjKqJL.ttf
418 ms
sdk.js
25 ms
113 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
71 ms
settings
169 ms
afflux.jp accessibility score
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
afflux.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
afflux.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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Afflux.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 Afflux.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.
afflux.jp
Open Graph description is not detected on the main page of AFFLUX. 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: