Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

dreamblog.jp

ドリーマ【dreama】|企業ホームページ・サイト制作は広島・岡山を中心に全国対応。ビジネス+ブログ+Eコマース+プロモーションツール(CMS)

Page Load Speed

4.7 sec in total

First Response

759 ms

Resources Loaded

3.7 sec

Page Rendered

248 ms

About Website

Click here to check amazing Dreamblog content for Philippines. Otherwise, check out these important facts you probably never knew about dreamblog.jp

ドリーマは、製作会社に頼らず自社内でWEBサイトやブログを構築・運用・販促活動ができるCMSです。また、ドリーマを利用したホームページ制作サービスのご案内も行っています。

Visit dreamblog.jp

Key Findings

We analyzed Dreamblog.jp page load time and found that the first response time was 759 ms and then it took 3.9 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

dreamblog.jp performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value330 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

dreamblog.jp

759 ms

portal.css

1474 ms

common.js

1189 ms

flash.js

1215 ms

jquery-1.4.4.min.js

495 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 21% of them (14 requests) were addressed to the original Dreamblog.jp, 41% (27 requests) were made to Dreama.jp and 9% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Dreama.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 87.7 kB (6%)

Content Size

1.5 MB

After Optimization

1.5 MB

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

HTML Optimization

-77%

Potential reduce by 39.7 kB

  • Original 51.6 kB
  • After minification 43.9 kB
  • After compression 11.8 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 7.7 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 39.7 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 44.5 kB

  • Original 1.3 MB
  • After minification 1.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. Dreamblog images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 200.3 kB
  • After minification 200.3 kB
  • After compression 198.6 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

-20%

Potential reduce by 1.7 kB

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

Requests Breakdown

Number of requests can be reduced by 26 (43%)

Requests Now

61

After Optimization

35

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

Accessibility Review

dreamblog.jp accessibility score

86

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

dreamblog.jp best practices score

58

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

Browser errors were logged to the console

SEO Factors

dreamblog.jp SEO score

69

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dreamblog.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 Dreamblog.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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