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

frantz.jp screenshot

23

Performance

Renders faster than
43% of other websites
51

Accessibility

Visual factors better than
that of 20% of websites
67

Best Practices

More advanced features
available than in
24% of websites
91

SEO

Google-friendlier than
71% of websites

First Response

552 ms

Resources Loaded

9.2 sec

Page Rendered

976 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 552 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value440 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.429

22/100

15%

TTI (Time to Interactive)

Value19.1 s

2/100

10%

frantz.jp

552 ms

www.frantz.jp

911 ms

base.css

358 ms

common.css

535 ms

sidebar.css

384 ms

Our browser made a total of 295 requests to load all elements on the main page. We found that 74% of them (219 requests) were addressed to the original Frantz.jp, 17% (50 requests) were made to Secure.future-s.com and 2% (6 requests) were made to Tradesafe.jp. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Secure.future-s.com.

Content Size

2.5 MB

After Optimization

2.0 MB

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

HTML Optimization

-79%

Potential reduce by 105.6 kB

Original 133.1 kB
After minification 123.6 kB
After compression 27.5 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 105.6 kB or 79% of the original size.

Image Optimization

-10%

Potential reduce by 216.3 kB

Original 2.2 MB
After minification 1.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

-60%

Potential reduce by 94.0 kB

Original 155.5 kB
After minification 148.8 kB
After compression 61.5 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 94.0 kB or 60% of the original size.

CSS Optimization

-81%

Potential reduce by 19.7 kB

Original 24.4 kB
After minification 16.5 kB
After compression 4.7 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 19.7 kB or 81% of the original size.

Requests Now

292

After Optimization

257

The browser has sent 292 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 17 to 1 for JavaScripts and from 9 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

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

SHIFT_JIS

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

frantz.jp

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