13.3 sec in total
1.2 sec
11.9 sec
241 ms
Welcome to loyalty.co.jp homepage info - get ready to check Loyalty best content for Japan right away, or after learning these important things about loyalty.co.jp
Loyalty Marketing, Inc. 株式会社 ロイヤリティ マーケティングの企業サイト。共通ポイントサービス「Ponta(ポンタ)」を運営。私たちは、培われた膨大なデータを駆使し、生活者・企業の皆様にとって、「真の価値ある情報」を提供いたします。
Visit loyalty.co.jpWe analyzed Loyalty.co.jp page load time and found that the first response time was 1.2 sec and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
loyalty.co.jp performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value47.3 s
0/100
25%
Value18.6 s
0/100
10%
Value980 ms
28/100
30%
Value0
100/100
15%
Value33.5 s
0/100
10%
1172 ms
803 ms
957 ms
384 ms
1338 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 69% of them (96 requests) were addressed to the original Loyalty.co.jp, 13% (18 requests) were made to Google.com and 10% (14 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Loyalty.co.jp.
Page size can be reduced by 1.0 MB (52%)
1.9 MB
925.4 kB
In fact, the total size of Loyalty.co.jp main page is 1.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. 45% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 8.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 8.5 kB or 71% of the original size.
Potential reduce by 221.6 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. Obviously, Loyalty needs image optimization as it can save up to 221.6 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 754.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 754.8 kB or 68% of the original size.
Potential reduce by 36.3 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. Loyalty.co.jp needs all CSS files to be minified and compressed as it can save up to 36.3 kB or 79% of the original size.
Number of requests can be reduced by 41 (30%)
137
96
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Loyalty. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and as a result speed up the page load time.
loyalty.co.jp
1172 ms
en
803 ms
style.css
957 ms
en.css
384 ms
jquery-1.10.2.min.js
1338 ms
jquery.easing.1.3.js
574 ms
jquery.transit.min.js
580 ms
searchua.js
751 ms
jquery.smoothScroll.js
762 ms
jquery.pass.js
962 ms
jquery.alignHeight.js
962 ms
jquery.responsive.js
1151 ms
easeljs-0.7.1.min.js
1910 ms
preloadjs-0.4.1.min.js
1907 ms
tweenjs-0.5.1.min.js
1717 ms
application.js
1541 ms
application-sp.js
1358 ms
highcharts.js
2719 ms
exporting.js
1930 ms
embed
174 ms
header_logo.png
396 ms
identity-circle.jpg
1327 ms
user3.png
396 ms
music1.png
397 ms
papers2.png
399 ms
piggy.png
398 ms
suitcase2.png
763 ms
calc.png
764 ms
tag.png
775 ms
brush.png
767 ms
cofeecup2.png
776 ms
heart.png
1146 ms
user2.png
1529 ms
car.png
1147 ms
folder3.png
1157 ms
backpack.png
1176 ms
lowson100.png
1523 ms
umbrella2.png
1526 ms
film.png
1540 ms
mobile.png
1559 ms
mcfly.png
1692 ms
newspaper.png
1905 ms
chopstick.png
1905 ms
rice.png
1909 ms
medicine.png
1930 ms
glasses.png
1941 ms
books.png
2075 ms
bus.png
2286 ms
papers1.png
2287 ms
briefcase.png
2299 ms
user1.png
2309 ms
floppy.png
2320 ms
folder2.png
2457 ms
letter.png
2669 ms
calendar.png
2670 ms
ga.js
22 ms
pc.png
2662 ms
__utm.gif
12 ms
js
65 ms
init_embed.js
20 ms
common.js
51 ms
map.js
51 ms
google4.png
15 ms
overlay.js
14 ms
util.js
78 ms
onion.js
75 ms
search_impl.js
76 ms
stats.js
39 ms
openhand_8_8.cur
31 ms
train.png
2299 ms
watch1.png
2313 ms
search.png
2448 ms
drop.png
2657 ms
transparent.png
33 ms
kh
70 ms
diamond2.png
2618 ms
ViewportInfoService.GetViewportInfo
75 ms
ViewportInfoService.GetViewportInfo
22 ms
controls.js
25 ms
css
59 ms
entity11.png
26 ms
ViewportInfoService.GetViewportInfo
26 ms
mapcnt6.png
30 ms
tmapctrl.png
18 ms
vt
103 ms
vt
147 ms
vt
90 ms
vt
97 ms
vt
105 ms
vt
79 ms
vt
137 ms
vt
161 ms
vt
152 ms
vt
158 ms
vt
168 ms
vt
204 ms
vt
219 ms
vt
213 ms
vt
221 ms
vt
218 ms
vt
225 ms
donut.png
2294 ms
camera.png
2292 ms
umbrella1.png
2323 ms
ponta.png
2467 ms
browser.png
2653 ms
AuthenticationService.Authenticate
13 ms
lowson.png
2289 ms
mic.png
2291 ms
music2.png
2283 ms
watch2.png
2294 ms
cofeecup1.png
2319 ms
hotdog.png
2283 ms
user4.png
2289 ms
diamond1.png
2291 ms
toaster.png
2282 ms
lock.png
2294 ms
muffin.png
2318 ms
pizza.png
2279 ms
folder1.png
2289 ms
giftbox.png
2288 ms
pencil.png
2269 ms
map2.png
2292 ms
suitcase1.png
2313 ms
identity-copy-01.png
2285 ms
identity-copy-02.png
2290 ms
identity-copy-03.png
2276 ms
identity-copy-04.png
2276 ms
identity-copy-05.png
2302 ms
ponta_logo.png
2887 ms
pagetop.png
2284 ms
footer-ponta-bg.png
2478 ms
footer-ponta-official@2x.png
2651 ms
footer-ponta-twitter@2x.png
2288 ms
footer-ponta-facebook@2x.png
2300 ms
footer-ponta-mixi@2x.png
2516 ms
privacy-75.gif
2313 ms
footer-copyright.png
3627 ms
QuotaService.RecordEvent
14 ms
loyalty.co.jp accessibility score
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
loyalty.co.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
Page has valid source maps
loyalty.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loyalty.co.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Loyalty.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.
loyalty.co.jp
Open Graph data is detected on the main page of Loyalty. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: