Tools & Wizards About Us
dream.jp screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

dream.jp

光回線、格安SIMサービスの「DTI」

Page Load Speed

4.5 sec in total

First Response

537 ms

Resources Loaded

3.7 sec

Page Rendered

353 ms

dream.jp screenshot

About Website

Click here to check amazing Dream content for Japan. Otherwise, check out these important facts you probably never knew about dream.jp

DTIでは、光回線接続サービス「DTI光」、格安SIMサービス「DTI SIM」など、便利でおトクなインターネット通信サービスを多数ご提供しています。

Visit dream.jp

Key Findings

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

Performance Metrics

dream.jp performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value460 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

dream.jp

537 ms

common.css

183 ms

header.css

388 ms

footer.css

403 ms

mobile.css

390 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 91% of them (50 requests) were addressed to the original Dream.jp, 4% (2 requests) were made to Googletagmanager.com and 2% (1 request) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Dream.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.5 kB (8%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dream.jp main page is 1.2 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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 23.4 kB

  • Original 30.1 kB
  • After minification 24.9 kB
  • After compression 6.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 5.1 kB, which is 17% 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 23.4 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 64.0 kB

  • Original 1.0 MB
  • After minification 978.7 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. Dream images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 7.2 kB

  • Original 111.9 kB
  • After minification 111.9 kB
  • After compression 104.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. This website has mostly compressed JavaScripts.

CSS Optimization

-18%

Potential reduce by 3.9 kB

  • Original 22.2 kB
  • After minification 22.2 kB
  • After compression 18.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. Dream.jp needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 18% of the original size.

Requests Breakdown

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

Requests Now

54

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dream.jp

dream.jp

537 ms

common.css

common.css

183 ms

header.css

header.css

388 ms

footer.css

footer.css

403 ms

mobile.css

mobile.css

390 ms

header-footer.css

header-footer.css

411 ms

top.css

top.css

392 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

582 ms

sns.js

sns.js

608 ms

globalheader.js

globalheader.js

605 ms

common_footer.js

common_footer.js

602 ms

mobile.js

mobile.js

601 ms

service_header.js

service_header.js

604 ms

announce.js

announce.js

761 ms

jquery.bxslider.js

jquery.bxslider.js

787 ms

jquery.tile.js

jquery.tile.js

798 ms

js

js

65 ms

js

js

94 ms

adsbygoogle.js

adsbygoogle.js

124 ms

css

css

33 ms

logo_dti.png

logo_dti.png

277 ms

banner_slider_hikari.png

banner_slider_hikari.png

750 ms

banner_slider_sim.png

banner_slider_sim.png

891 ms

banner_slider_wimax.png

banner_slider_wimax.png

1290 ms

banner_slider_docomo.png

banner_slider_docomo.png

585 ms

banner_slider_ipv6.png

banner_slider_ipv6.png

891 ms

icon_ftth_dtihikari.png

icon_ftth_dtihikari.png

416 ms

icon_mb_sim.png

icon_mb_sim.png

596 ms

icon_mb_wm.png

icon_mb_wm.png

775 ms

icon_ftth_docomohikari.png

icon_ftth_docomohikari.png

776 ms

icon_ftth_auhikari.png

icon_ftth_auhikari.png

934 ms

icon_ftth_dtihikarisimple.png

icon_ftth_dtihikarisimple.png

968 ms

icon_cloud_vps.png

icon_cloud_vps.png

958 ms

icon_cloud_disk.png

icon_cloud_disk.png

1077 ms

icon_ipv6.png

icon_ipv6.png

1072 ms

dtihikari_top_banner.png

dtihikari_top_banner.png

1119 ms

banner_bottom_1214-05.png

banner_bottom_1214-05.png

1155 ms

banner_bottom_1214-06.png

banner_bottom_1214-06.png

1334 ms

logo_dti_white.png

logo_dti_white.png

1252 ms

PI-ICT_Mark.png

PI-ICT_Mark.png

1256 ms

header_ic01.png

header_ic01.png

1292 ms

header_ic02.png

header_ic02.png

1330 ms

bg_toppage_servicemenu.gif

bg_toppage_servicemenu.gif

1431 ms

bg_toppage_servicemenu_left.gif

bg_toppage_servicemenu_left.gif

1426 ms

bg_toppage_servicemenu_right.gif

bg_toppage_servicemenu_right.gif

1468 ms

sitemap_ic01.png

sitemap_ic01.png

1474 ms

isp_ic.png

isp_ic.png

1508 ms

font

font

26 ms

info_dream.php

info_dream.php

1681 ms

banner_slider_hikari.png

banner_slider_hikari.png

397 ms

banner_slider_ipv6.png

banner_slider_ipv6.png

396 ms

banner_slider_sim.png

banner_slider_sim.png

777 ms

banner_slider_wimax.png

banner_slider_wimax.png

581 ms

banner_slider_docomo.png

banner_slider_docomo.png

398 ms

controls02.png

controls02.png

576 ms

Accessibility Review

dream.jp accessibility score

71

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

dream.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

dream.jp SEO score

92

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

dream.jp

Open Graph data is detected on the main page of Dream. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: