Tools & Wizards About Us
dlife.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

dlife.jp

【公式】Dlife（ディーライフ）

Page Load Speed

10.7 sec in total

First Response

388 ms

Resources Loaded

10 sec

Page Rendered

374 ms

dlife.jp screenshot

About Website

Welcome to dlife.jp homepage info - get ready to check Dlife best content for Japan right away, or after learning these important things about dlife.jp

長きにわたって愛される海外ドラマシリーズから、日本初放送作品まで、これまでもこれからも世界中から選りすぐった至極のドラマを中心に良質な作品をお届けします。「FOX」チャンネルの名称は2024年3月1日から「Dlife」に変更になりました。

Visit dlife.jp

Key Findings

We analyzed Dlife.jp page load time and found that the first response time was 388 ms and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

dlife.jp performance score

0

Network Requests Diagram

dlife.jp

388 ms

www.dlife.jp

2373 ms

reset2.css

379 ms

base2.css

728 ms

PI_style2.css

742 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 66% of them (70 requests) were addressed to the original Dlife.jp, 9% (10 requests) were made to Static.xx.fbcdn.net and 7% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Dlife.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 342.4 kB (21%)

Content Size

1.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dlife.jp main page is 1.7 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. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-50%

Potential reduce by 93.3 kB

  • Original 185.0 kB
  • After minification 158.1 kB
  • After compression 91.7 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 26.9 kB, which is 15% 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 93.3 kB or 50% of the original size.

Image Optimization

-3%

Potential reduce by 30.7 kB

  • Original 1.1 MB
  • After minification 1.1 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. Dlife images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 159.2 kB

  • Original 239.2 kB
  • After minification 180.0 kB
  • After compression 80.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 159.2 kB or 67% of the original size.

CSS Optimization

-65%

Potential reduce by 59.3 kB

  • Original 91.5 kB
  • After minification 71.2 kB
  • After compression 32.2 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. Dlife.jp needs all CSS files to be minified and compressed as it can save up to 59.3 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (52%)

Requests Now

103

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dlife.jp

dlife.jp

388 ms

www.dlife.jp

www.dlife.jp

2373 ms

reset2.css

reset2.css

379 ms

base2.css

base2.css

728 ms

PI_style2.css

PI_style2.css

742 ms

slide2.css

slide2.css

372 ms

shadowbox.css

shadowbox.css

376 ms

shadowbox-video.css

shadowbox-video.css

560 ms

expandbanner.css

expandbanner.css

745 ms

jquery.js

jquery.js

1105 ms

drupal.js

drupal.js

752 ms

ja_5efac26ef4c2fdf6a5db9e8333b2d878.js

ja_5efac26ef4c2fdf6a5db9e8333b2d878.js

931 ms

googleanalytics.js

googleanalytics.js

1101 ms

jquery.min.js

jquery.min.js

49 ms

jquery.cookie.js

jquery.cookie.js

1131 ms

slick.min.js

slick.min.js

5 ms

mega_menu.css

mega_menu.css

981 ms

heightLine.js

heightLine.js

982 ms

common.js

common.js

1115 ms

rollover.js

rollover.js

1289 ms

tip.js

tip.js

1286 ms

jquery.easyListSplitter.js

jquery.easyListSplitter.js

1297 ms

mega_menu.js

mega_menu.js

1294 ms

common2.js

common2.js

1338 ms

shadowbox.js

shadowbox.js

1840 ms

shadowbox-video.js

shadowbox-video.js

1664 ms

expandbanner.js

expandbanner.js

1659 ms

bl_track.js

bl_track.js

332 ms

wdigWebAnalytics.js

wdigWebAnalytics.js

56 ms

dlife_logo.png

dlife_logo.png

1037 ms

btn_slideDetail.png

btn_slideDetail.png

698 ms

mainareaA_1.jpg

mainareaA_1.jpg

1791 ms

mainareaA_2.jpg

mainareaA_2.jpg

1762 ms

mainareaA_3.jpg

mainareaA_3.jpg

1776 ms

mainareaA_4.jpg

mainareaA_4.jpg

1956 ms

mainareaA_5.jpg

mainareaA_5.jpg

2117 ms

mainareaA_6.jpg

mainareaA_6.jpg

2656 ms

ttl_side_now.png

ttl_side_now.png

2140 ms

item_attention.png

item_attention.png

2152 ms

pickup_1.jpg

pickup_1.jpg

2162 ms

btn_pickDetail.png

btn_pickDetail.png

2324 ms

pickup_2.jpg

pickup_2.jpg

2487 ms

pickup_3.jpg

pickup_3.jpg

2910 ms

pickup_4.jpg

pickup_4.jpg

2520 ms

pickup_5.jpg

pickup_5.jpg

2542 ms

pickup_6.jpg

pickup_6.jpg

2694 ms

pickup_7.jpg

pickup_7.jpg

3219 ms

pickup_8.jpg

pickup_8.jpg

3253 ms

pickup_9.jpg

pickup_9.jpg

2913 ms

pickup_10.jpg

pickup_10.jpg

3386 ms

pickup_11.jpg

pickup_11.jpg

3105 ms

pickup_12.jpg

pickup_12.jpg

3646 ms

pickup_13.jpg

pickup_13.jpg

3652 ms

pickup_14.jpg

pickup_14.jpg

3838 ms

item_whats.png

item_whats.png

3599 ms

btn_whatsmore.png

btn_whatsmore.png

3574 ms

likebox.php

likebox.php

107 ms

widgets.js

widgets.js

22 ms

top_bnr_img.png

top_bnr_img.png

4338 ms

xYm_UD1pmAz.css

xYm_UD1pmAz.css

95 ms

TGpOWuX6Pv8.css

TGpOWuX6Pv8.css

115 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

155 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

182 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

150 ms

TTCre3391I0.js

TTCre3391I0.js

152 ms

sidebnr_app_05.jpg

sidebnr_app_05.jpg

3729 ms

sidebnr_tsumtsum_started.jpg

sidebnr_tsumtsum_started.jpg

4050 ms

sidebnr_toy.jpg

sidebnr_toy.jpg

4426 ms

item_tokusetsu.png

item_tokusetsu.png

3706 ms

side_shield.jpg

side_shield.jpg

3848 ms

12744547_1053189678037919_1747711480222568223_n.jpg

12744547_1053189678037919_1747711480222568223_n.jpg

101 ms

603579_706616709361886_954026872_n.jpg

603579_706616709361886_954026872_n.jpg

80 ms

10981518_102090616805345_8776720878030356753_n.jpg

10981518_102090616805345_8776720878030356753_n.jpg

85 ms

12495186_822644237862368_6437417928251961682_n.jpg

12495186_822644237862368_6437417928251961682_n.jpg

85 ms

947376_133440633518497_1444884934_n.jpg

947376_133440633518497_1444884934_n.jpg

93 ms

11148792_770756669718022_7934594836839322445_n.jpg

11148792_770756669718022_7934594836839322445_n.jpg

94 ms

12790843_812040035591257_245198651492053946_n.jpg

12790843_812040035591257_245198651492053946_n.jpg

100 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

30 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

30 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

23 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

39 ms

side_csi.jpg

side_csi.jpg

4078 ms

sidebnr_criminalminds.jpg

sidebnr_criminalminds.jpg

4074 ms

side_ep1.png

side_ep1.png

4255 ms

ga.js

ga.js

39 ms

dlife.jp.js

dlife.jp.js

193 ms

item_Dlifeofficial.png

item_Dlifeofficial.png

3870 ms

bl_track.cgi

bl_track.cgi

362 ms

__utm.gif

__utm.gif

14 ms

ttl_side_follow.png

ttl_side_follow.png

3820 ms

wdigWebAnalyticsFunctions.js

wdigWebAnalyticsFunctions.js

54 ms

tagsv2.php

tagsv2.php

215 ms

s_code.js

s_code.js

67 ms

error.js

error.js

48 ms

post_process.js

post_process.js

61 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

22 ms

s96410982515662

s96410982515662

13 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

16 ms

jot

jot

89 ms

item_info.png

item_info.png

3362 ms

side_bnr_audience2.png

side_bnr_audience2.png

3346 ms

side_bnr_change2.png

side_bnr_change2.png

3350 ms

footer_pixa.jpg

footer_pixa.jpg

3880 ms

top_bnr_bg_03.png

top_bnr_bg_03.png

3117 ms

bg_wrap01.png

bg_wrap01.png

3547 ms

sbpu.css

sbpu.css

379 ms

SEO Factors

dlife.jp SEO score

0

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 Dlife.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 Dlife.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.

Social Sharing Optimization

dlife.jp

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