Access d-berry.jp. ホームページ制作埼玉 | デジタルベリー

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

d-berry.jp

582 ms

www.d-berry.jp

899 ms

cmn_reset.css

176 ms

cmn_style.css

351 ms

slick.css

501 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 88% of them (70 requests) were addressed to the original D-berry.jp, 5% (4 requests) were made to Fonts.googleapis.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain D-berry.jp.

Content Size

1.2 MB

After Optimization

1.1 MB

In fact, the total size of D-berry.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 37.0 kB

Original 45.4 kB
After minification 40.1 kB
After compression 8.4 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.3 kB, which is 12% 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 37.0 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 84.2 kB

Original 1.1 MB
After minification 995.8 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. D Berry images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 9.8 kB

Original 55.7 kB
After minification 55.1 kB
After compression 45.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 9.8 kB or 18% of the original size.

CSS Optimization

-35%

Potential reduce by 5.3 kB

Original 14.9 kB
After minification 14.9 kB
After compression 9.6 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. D-berry.jp needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 35% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

These are opportunities to improve the legibility of your content.

High

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

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.

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

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 D-berry.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 D-berry.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

d-berry.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

ホームページ制作 埼玉 | デジタルベリー | さいたま市のWeb制作

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

d-berry.jp

www.d-berry.jp

cmn_reset.css

cmn_style.css

slick.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

d-berry.jp

www.d-berry.jp

cmn_reset.css

cmn_style.css

slick.css

style.css

css2

jquery-3.6.3.min.js

slick.min.js

lozad.js

backtop.js

zdo_drawer_menu.js

jquery.rwdImageMaps.js

ofi.min.js

fitie.js

hpstat.js

css2

css2

css2

gtm.js

body_bg.jpg

sp_icon01.png

sp_icon02.png

header_logo.svg

footer_icon03.png

header_nav_tab.png

header_btn_dataup.png

header-tel-icon.png

header-mail-icon.png

movie_bg.png

top_main_visual.png

visual_message1.png

bnr01.png

cap_saitama_img.png

cap_nitori_img.png

cap_kawasaki_img.png

cap_senior_img.png

cap_saitamaresona_img.png

cap_blluna_img.png

cap_saitama-jibun-design_img.jpg

cap_hiltontokyo_img.png

cap_seibu_img.png

cap_iwatani_img.png

ホームページ制作埼玉 | デジタルベリー | さいたま市のWeb制作