Tools & Wizards About Us
jp.onduline.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

jp.onduline.com

オンデュリン　オフィシャルホームページ

Page Load Speed

4.5 sec in total

First Response

659 ms

Resources Loaded

3.7 sec

Page Rendered

83 ms

jp.onduline.com screenshot

About Website

Visit jp.onduline.com now to see the best up-to-date Jp Onduline content for Turkey and also check out these interesting facts you probably never knew about jp.onduline.com

オンデュリン屋根材システム

Visit jp.onduline.com

Key Findings

We analyzed Jp.onduline.com page load time and found that the first response time was 659 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

jp.onduline.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value18.0 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value1,920 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.316

37/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

jp.onduline.com

659 ms

css_TdeVS_i4VL3EwCH-NZa3WOs6vMXVvnMrX3oQy3aBsWE.css

86 ms

css_hYCLW089C9S9sP3ZYkuG6R-Q5ZHbEhblZBFjwZ_bE_I.css

165 ms

css_lvHShG76JuSBtlKE4yLO7X0DxIhWlN2OpMcrmdenQLE.css

169 ms

css_Yh-eR9qzvZ_kAchcAAWONlCa1duk40-lsP5TFFCnGP8.css

182 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 73% of them (30 requests) were addressed to the original Jp.onduline.com, 20% (8 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Jp.onduline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 501.2 kB (13%)

Content Size

3.8 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jp.onduline.com main page is 3.8 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. 70% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 17.9 kB

  • Original 24.1 kB
  • After minification 22.8 kB
  • After compression 6.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. 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 17.9 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 47.1 kB

  • Original 3.2 MB
  • After minification 3.2 MB

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. Jp Onduline images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 362.4 kB

  • Original 476.1 kB
  • After minification 382.6 kB
  • After compression 113.7 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 362.4 kB or 76% of the original size.

CSS Optimization

-81%

Potential reduce by 73.9 kB

  • Original 90.6 kB
  • After minification 88.8 kB
  • After compression 16.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. Jp.onduline.com needs all CSS files to be minified and compressed as it can save up to 73.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (31%)

Requests Now

32

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jp Onduline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

jp.onduline.com

jp.onduline.com

659 ms

css_TdeVS_i4VL3EwCH-NZa3WOs6vMXVvnMrX3oQy3aBsWE.css

css_TdeVS_i4VL3EwCH-NZa3WOs6vMXVvnMrX3oQy3aBsWE.css

86 ms

css_hYCLW089C9S9sP3ZYkuG6R-Q5ZHbEhblZBFjwZ_bE_I.css

css_hYCLW089C9S9sP3ZYkuG6R-Q5ZHbEhblZBFjwZ_bE_I.css

165 ms

css_lvHShG76JuSBtlKE4yLO7X0DxIhWlN2OpMcrmdenQLE.css

css_lvHShG76JuSBtlKE4yLO7X0DxIhWlN2OpMcrmdenQLE.css

169 ms

css_Yh-eR9qzvZ_kAchcAAWONlCa1duk40-lsP5TFFCnGP8.css

css_Yh-eR9qzvZ_kAchcAAWONlCa1duk40-lsP5TFFCnGP8.css

182 ms

css

css

27 ms

js_0qlzNmRd5eIzax2ZtoBiFWuErHnH9F8BMadDVEP1yxs.js

js_0qlzNmRd5eIzax2ZtoBiFWuErHnH9F8BMadDVEP1yxs.js

273 ms

js_uj1NAy_6CBiEHlFTpi1OzEkpZph4X5Sgp1rL5v1K1hQ.js

js_uj1NAy_6CBiEHlFTpi1OzEkpZph4X5Sgp1rL5v1K1hQ.js

190 ms

lightbox.js

lightbox.js

1163 ms

js_I8yX6RYPZb7AtMcDUA3QKDZqVkvEn35ED11_1i7vVpc.js

js_I8yX6RYPZb7AtMcDUA3QKDZqVkvEn35ED11_1i7vVpc.js

244 ms

js_02bLdsEmeoVhbQEYgYKaWwgn6LhCl9g6O0dOu5GnBx8.js

js_02bLdsEmeoVhbQEYgYKaWwgn6LhCl9g6O0dOu5GnBx8.js

508 ms

analytics.js

analytics.js

85 ms

logo_4.png

logo_4.png

85 ms

menu-line.png

menu-line.png

90 ms

menu-expanded.png

menu-expanded.png

83 ms

menu-arrow.png

menu-arrow.png

109 ms

sub-menu-bg.png

sub-menu-bg.png

91 ms

menu-leaf.png

menu-leaf.png

91 ms

youtube.png

youtube.png

165 ms

searchbar.png

searchbar.png

168 ms

search-button.png

search-button.png

178 ms

dopa001_1.jpg

dopa001_1.jpg

882 ms

MrY.png

MrY.png

1718 ms

sheets22.jpg

sheets22.jpg

180 ms

push_home_large.png

push_home_large.png

246 ms

Sans%20titre-1_1.jpg

Sans%20titre-1_1.jpg

252 ms

Fotolia_41981171_M.jpg

Fotolia_41981171_M.jpg

266 ms

see-more.png

see-more.png

267 ms

foot-sep.png

foot-sep.png

327 ms

bulle.png

bulle.png

418 ms

puces.png

puces.png

355 ms

IgZJs4-7SA1XX_edsoXWog.ttf

IgZJs4-7SA1XX_edsoXWog.ttf

21 ms

DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf

DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf

49 ms

MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf

MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf

49 ms

k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf

k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf

47 ms

PRmiXeptR36kaC0GEAetxi9-WlPSxbfiI49GsXo3q0g.ttf

PRmiXeptR36kaC0GEAetxi9-WlPSxbfiI49GsXo3q0g.ttf

49 ms

O4NhV7_qs9r9seTo7fnsVKCWcynf_cDxXwCLxiixG1c.ttf

O4NhV7_qs9r9seTo7fnsVKCWcynf_cDxXwCLxiixG1c.ttf

49 ms

PRmiXeptR36kaC0GEAetxpZ7xm-Bj30Bj2KNdXDzSZg.ttf

PRmiXeptR36kaC0GEAetxpZ7xm-Bj30Bj2KNdXDzSZg.ttf

50 ms

PRmiXeptR36kaC0GEAetxne1Pd76Vl7zRpE7NLJQ7XU.ttf

PRmiXeptR36kaC0GEAetxne1Pd76Vl7zRpE7NLJQ7XU.ttf

48 ms

collect

collect

14 ms

css_3XBA5gBq5QJGreaWy3k-VTkuNQcoxyeDlf6MFSWaQpU.css

css_3XBA5gBq5QJGreaWy3k-VTkuNQcoxyeDlf6MFSWaQpU.css

86 ms

Accessibility Review

jp.onduline.com accessibility score

93

Accessibility Issues

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

High

[role]s do not have all required [aria-*] attributes

Best Practices

jp.onduline.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

jp.onduline.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jp.onduline.com 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 Jp.onduline.com 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.

Social Sharing Optimization

jp.onduline.com

Open Graph description is not detected on the main page of Jp Onduline. 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: