Tools & Wizards About Us
palace-iwaya.jp screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

palace-iwaya.jp

【公式】PALACE IWAYA［パレスいわや］｜福島県いわき市の結婚式場

Page Load Speed

8.2 sec in total

First Response

562 ms

Resources Loaded

6.8 sec

Page Rendered

745 ms

palace-iwaya.jp screenshot

About Website

Welcome to palace-iwaya.jp homepage info - get ready to check PALACE IWAYA best content for Japan right away, or after learning these important things about palace-iwaya.jp

福島県いわき市の結婚式場パレスいわや［PALACE IWAYA］の公式ホームページ。結婚式やフォトウェディングだけでなく、ご宴会や成人式のお祝いなど多彩な目的にあわせて、こだわりの料理とプランをご提案いたします。創業より変わらず大切にしてきた「もてなしの心」の極みがここにあります。

Visit palace-iwaya.jp

Key Findings

We analyzed Palace-iwaya.jp page load time and found that the first response time was 562 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

palace-iwaya.jp performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value1,040 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

palace-iwaya.jp

562 ms

www.palace-iwaya.jp

1335 ms

swiper.css

29 ms

slick.css

546 ms

slick-theme.css

558 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 87% of them (91 requests) were addressed to the original Palace-iwaya.jp, 4% (4 requests) were made to Fonts.googleapis.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Palace-iwaya.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 406.4 kB (2%)

Content Size

18.0 MB

After Optimization

17.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Palace-iwaya.jp main page is 18.0 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 17.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 58.3 kB

  • Original 69.8 kB
  • After minification 63.5 kB
  • After compression 11.6 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 58.3 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 163.6 kB

  • Original 17.7 MB
  • After minification 17.5 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. PALACE IWAYA images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 67.0 kB

  • Original 89.2 kB
  • After minification 76.4 kB
  • After compression 22.2 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 67.0 kB or 75% of the original size.

CSS Optimization

-87%

Potential reduce by 117.5 kB

  • Original 134.6 kB
  • After minification 105.6 kB
  • After compression 17.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. Palace-iwaya.jp needs all CSS files to be minified and compressed as it can save up to 117.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (48%)

Requests Now

100

After Optimization

52

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

palace-iwaya.jp

palace-iwaya.jp

562 ms

www.palace-iwaya.jp

www.palace-iwaya.jp

1335 ms

swiper.css

swiper.css

29 ms

slick.css

slick.css

546 ms

slick-theme.css

slick-theme.css

558 ms

styles2.css

styles2.css

560 ms

zoomslider.css

zoomslider.css

562 ms

js

js

60 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

15 ms

jquery-ui.js

jquery-ui.js

19 ms

swiper.jquery.min.js

swiper.jquery.min.js

130 ms

slick.min.js

slick.min.js

399 ms

jquery.matchHeight.js

jquery.matchHeight.js

355 ms

effect.js

effect.js

370 ms

common.js

common.js

374 ms

grt-youtube-popup.js

grt-youtube-popup.js

375 ms

functions.js

functions.js

535 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

741 ms

jquery.zoomslider.min.js

jquery.zoomslider.min.js

561 ms

reset.css

reset.css

376 ms

common.css

common.css

376 ms

common_sp.css

common_sp.css

405 ms

common_pc.css

common_pc.css

530 ms

sp2.css

sp2.css

748 ms

pc2.css

pc2.css

562 ms

css

css

30 ms

css

css

45 ms

css

css

49 ms

hannari.css

hannari.css

49 ms

gtm.js

gtm.js

127 ms

gtm.js

gtm.js

215 ms

common.css

common.css

276 ms

logo.png

logo.png

274 ms

icon_tell.png

icon_tell.png

269 ms

icon_cal.png

icon_cal.png

280 ms

icon_cal_why.png

icon_cal_why.png

273 ms

icon_cal_brw.png

icon_cal_brw.png

274 ms

icon_f_gry.png

icon_f_gry.png

450 ms

icon_t_gry.png

icon_t_gry.png

457 ms

icon_i_gry.png

icon_i_gry.png

463 ms

icon_tiktok_gry.png

icon_tiktok_gry.png

462 ms

concept_bnr_pc.png

concept_bnr_pc.png

1211 ms

fair_arrow.png

fair_arrow.png

474 ms

arrow_gold.png

arrow_gold.png

631 ms

wfair_main_images02_M.jpg

wfair_main_images02_M.jpg

1569 ms

wfair_main_images02_M.jpg

wfair_main_images02_M.jpg

1580 ms

wfair_main_images02_M.jpg

wfair_main_images02_M.jpg

2144 ms

wfair_main_images02_M.jpg

wfair_main_images02_M.jpg

1244 ms

wfair_main_images02_M.jpg

wfair_main_images02_M.jpg

1357 ms

arrow_wht.png

arrow_wht.png

1396 ms

stories_pic01_pc.png

stories_pic01_pc.png

1823 ms

stories_pic02_pc.png

stories_pic02_pc.png

1719 ms

style_01.png

style_01.png

1584 ms

style_02.png

style_02.png

1756 ms

style_03.png

style_03.png

1953 ms

plan_pic_pc.png

plan_pic_pc.png

1962 ms

cuisine_pic_pc.png

cuisine_pic_pc.png

2085 ms

chef_01_sp.png

chef_01_sp.png

1941 ms

chef_02.png

chef_02.png

2015 ms

ceremony_slide01_pc.png

ceremony_slide01_pc.png

2129 ms

ceremony_slide02_pc.png

ceremony_slide02_pc.png

2327 ms

party_slide01_pc.png

party_slide01_pc.png

2151 ms

party_slide02_pc.png

party_slide02_pc.png

2210 ms

party_slide03_pc.png

party_slide03_pc.png

2267 ms

party_slide05_pc.png

party_slide05_pc.png

2317 ms

party_slide04_pc.png

party_slide04_pc.png

3076 ms

party_slide06_pc.png

party_slide06_pc.png

2233 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1g.ttf

89 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfY3lCA.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfY3lCA.ttf

107 ms

Hannari-Regular.woff

Hannari-Regular.woff

108 ms

dress_pic_pc.png

dress_pic_pc.png

2142 ms

arrow_brw.png

arrow_brw.png

2181 ms

arrow_sq_wht.png

arrow_sq_wht.png

2232 ms

engagement_pic.png

engagement_pic.png

2244 ms

party_mice_pic.png

party_mice_pic.png

2258 ms

access_pic.png

access_pic.png

2324 ms

enkai_bnr_pc.png

enkai_bnr_pc.png

2185 ms

seijinshiki_bnr_pc.png

seijinshiki_bnr_pc.png

2234 ms

ysons_bnr_pc.png

ysons_bnr_pc.png

2243 ms

corona_bnr_pc.png

corona_bnr_pc.png

2258 ms

icon_f_sp.png

icon_f_sp.png

2324 ms

icon_t_sp.png

icon_t_sp.png

2185 ms

icon_i_sp.png

icon_i_sp.png

1667 ms

icon_tiktok_sp.png

icon_tiktok_sp.png

1647 ms

footer_logo.png

footer_logo.png

1552 ms

icon_f_wht.png

icon_f_wht.png

1593 ms

icon_t_wht.png

icon_t_wht.png

1429 ms

icon_i_wht.png

icon_i_wht.png

1483 ms

icon_tiktok_wht.png

icon_tiktok_wht.png

1494 ms

f_logo01.png

f_logo01.png

1376 ms

f_logo02.png

f_logo02.png

1426 ms

key_06_pc.png

key_06_pc.png

1360 ms

key_06_sp.png

key_06_sp.png

1307 ms

key_02_pc.png

key_02_pc.png

207 ms

key_01_pc.png

key_01_pc.png

380 ms

key_03_pc.png

key_03_pc.png

189 ms

key_04_pc.png

key_04_pc.png

204 ms

key_05_pc.png

key_05_pc.png

205 ms

slide_prev.png

slide_prev.png

188 ms

slide_next.png

slide_next.png

188 ms

ajax-loader.gif

ajax-loader.gif

183 ms

arrow_sq_gry_prev.png

arrow_sq_gry_prev.png

195 ms

arrow_sq_gry_next.png

arrow_sq_gry_next.png

186 ms

arrow_sq_wht_prev.png

arrow_sq_wht_prev.png

187 ms

arrow_sq_wht_next.png

arrow_sq_wht_next.png

363 ms

Accessibility Review

palace-iwaya.jp accessibility score

81

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.

Tables and lists

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

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

palace-iwaya.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

palace-iwaya.jp SEO score

95

Search Engine Optimization Advices

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

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 Palace-iwaya.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 Palace-iwaya.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

palace-iwaya.jp

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