Access frantz.jp. 神戸フランツ-スイーツギフトやプレゼントのオンラインショッピング【通販】

frantz.jp screenshot

15

Performance

Renders faster than
27% of other websites
51

Accessibility

Visual factors better than
that of 21% of websites
58

Best Practices

More advanced features
available than in
20% of websites
91

SEO

Google-friendlier than
70% of websites

First Response

531 ms

Resources Loaded

9.1 sec

Page Rendered

707 ms

frantz.jp screenshot

About Website

Visit frantz.jp now to see the best up-to-date Frantz content for Japan and also check out these interesting facts you probably never knew about frantz.jp

父の日ギフトや母の日のプレゼント、敬老の日の贈り物・お歳暮やお中元や・バレンタインの本命チョコや義理チョコ・ホワイトデーのお返しスイーツ・クリスマスケーキになどのギフト時期には欠かせない魅力的なスイーツギフトやプチギフト等のお取り寄せスイーツの神戸フランツ。

Visit frantz.jp

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value13.2 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.368

29/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

frantz.jp

531 ms

www.frantz.jp

544 ms

www.frantz.jp

905 ms

base.css

353 ms

common.css

516 ms

Our browser made a total of 214 requests to load all elements on the main page. We found that 80% of them (172 requests) were addressed to the original Frantz.jp, 9% (20 requests) were made to Frantz.fs-storage.jp and 2% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Frantz.fs-storage.jp.

Content Size

4.2 MB

After Optimization

4.1 MB

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

HTML Optimization

-81%

Potential reduce by 110.0 kB

Original 135.9 kB
After minification 122.0 kB
After compression 25.9 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 110.0 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 11.8 kB

Original 3.9 MB
After minification 3.9 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. Frantz images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 25.0 kB

Original 166.3 kB
After minification 164.1 kB
After compression 141.3 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 25.0 kB or 15% of the original size.

CSS Optimization

-71%

Potential reduce by 12.2 kB

Original 17.2 kB
After minification 13.0 kB
After compression 5.0 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. Frantz.jp needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 71% of the original size.

Requests Now

210

After Optimization

177

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

Accessibility Issues

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

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

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

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

N/A
Encoding

UTF-8

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

frantz.jp

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