Tools & Wizards About Us
portom.jp screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

portom.jp

【Official】PORTOM INTERNATIONAL HOKKAIDO / Hotel Directly Connected to New Chitose Airport

Page Load Speed

12.7 sec in total

First Response

530 ms

Resources Loaded

10.8 sec

Page Rendered

1.3 sec

portom.jp screenshot

About Website

Click here to check amazing PORTOM content. Otherwise, check out these important facts you probably never knew about portom.jp

PORTOM INTERNATIONAL HOKKAIDO is a premium hotel directly connected to the New Chitose Airport. With the concept of

Visit portom.jp

Key Findings

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

Performance Metrics

portom.jp performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value19.3 s

0/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

portom.jp

530 ms

portom.jp

696 ms

www.portom.jp

1248 ms

gtm.js

97 ms

common.css

516 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 77% of them (59 requests) were addressed to the original Portom.jp, 6% (5 requests) were made to Cdn.jsdelivr.net and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Portom.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 305.6 kB (10%)

Content Size

3.1 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Portom.jp main page is 3.1 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 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 92.1 kB

  • Original 112.0 kB
  • After minification 98.3 kB
  • After compression 19.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 13.7 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 92.1 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 104.0 kB

  • Original 2.8 MB
  • After minification 2.7 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. PORTOM images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 101.0 kB

  • Original 191.7 kB
  • After minification 191.7 kB
  • After compression 90.7 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 101.0 kB or 53% of the original size.

CSS Optimization

-25%

Potential reduce by 8.5 kB

  • Original 34.8 kB
  • After minification 34.8 kB
  • After compression 26.3 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. Portom.jp needs all CSS files to be minified and compressed as it can save up to 8.5 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (22%)

Requests Now

69

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

portom.jp

portom.jp

530 ms

portom.jp

portom.jp

696 ms

www.portom.jp

www.portom.jp

1248 ms

gtm.js

gtm.js

97 ms

common.css

common.css

516 ms

css2

css2

38 ms

font-awesome.min.css

font-awesome.min.css

25 ms

jquery-ui.min.css

jquery-ui.min.css

512 ms

slick.min.css

slick.min.css

29 ms

homepage.css

homepage.css

692 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

36 ms

common.min.js

common.min.js

530 ms

jquery-ui.min.js

jquery-ui.min.js

735 ms

search.min.js

search.min.js

576 ms

slick.min.js

slick.min.js

31 ms

vivus.min.js

vivus.min.js

30 ms

homepage.min.js

homepage.min.js

1020 ms

tc_widget.js

tc_widget.js

1219 ms

js

js

79 ms

analytics.js

analytics.js

22 ms

collect

collect

20 ms

collect

collect

33 ms

ga-audiences

ga-audiences

67 ms

img_poster.jpg

img_poster.jpg

852 ms

image_20210730125009_1_l.jpg

image_20210730125009_1_l.jpg

1413 ms

img_mainimg.jpg

img_mainimg.jpg

1138 ms

base.svg

base.svg

490 ms

img_art1.jpg

img_art1.jpg

816 ms

img_art2.jpg

img_art2.jpg

704 ms

img_art3.jpg

img_art3.jpg

1058 ms

img_art4.jpg

img_art4.jpg

1171 ms

img_art5.jpg

img_art5.jpg

1558 ms

img_art9.jpg

img_art9.jpg

1372 ms

img_art10.jpg

img_art10.jpg

1507 ms

img_exp2.jpg

img_exp2.jpg

1869 ms

img_din1_1.jpg

img_din1_1.jpg

2190 ms

ic_shimo.png

ic_shimo.png

1672 ms

img_din1_2.jpg

img_din1_2.jpg

2427 ms

ic_tate.png

ic_tate.png

2035 ms

img_din2_1.jpg

img_din2_1.jpg

2367 ms

img_din2_2.jpg

img_din2_2.jpg

2551 ms

img_spa1.jpg

img_spa1.jpg

2877 ms

img_spa2.jpg

img_spa2.jpg

3053 ms

img_sta1.jpg

img_sta1.jpg

3418 ms

img_sta2.jpg

img_sta2.jpg

3557 ms

img_sta3.jpg

img_sta3.jpg

3657 ms

img_sta4.jpg

img_sta4.jpg

4064 ms

img_sta5.jpg

img_sta5.jpg

4177 ms

bg1.jpg

bg1.jpg

3542 ms

800x533_ea1e9d427fb5664c32c517a73e421e58_c50abc104352b3f4ca6d38b8ea020cc4db6bbdab.png

800x533_ea1e9d427fb5664c32c517a73e421e58_c50abc104352b3f4ca6d38b8ea020cc4db6bbdab.png

4469 ms

noimage.gif

noimage.gif

4069 ms

800x533_ea1e9d427fb5664c32c517a73e421e58_d4dfff8ffb6459efcdad5a0b7766761603583be7.jpg

800x533_ea1e9d427fb5664c32c517a73e421e58_d4dfff8ffb6459efcdad5a0b7766761603583be7.jpg

4581 ms

800x533_ea1e9d427fb5664c32c517a73e421e58_c3585092a2ba88b8175957af95b68297f2070992.jpg

800x533_ea1e9d427fb5664c32c517a73e421e58_c3585092a2ba88b8175957af95b68297f2070992.jpg

4500 ms

800x533_ea1e9d427fb5664c32c517a73e421e58_39cb988b497e71f948afc58ad2e5a6d86fc3d7ed.jpg

800x533_ea1e9d427fb5664c32c517a73e421e58_39cb988b497e71f948afc58ad2e5a6d86fc3d7ed.jpg

5115 ms

800x533_ea1e9d427fb5664c32c517a73e421e58_8fbc45dc75eb440dd3680a811e65f1c667e0b0b3.jpg

800x533_ea1e9d427fb5664c32c517a73e421e58_8fbc45dc75eb440dd3680a811e65f1c667e0b0b3.jpg

4938 ms

img_lnk2.jpg

img_lnk2.jpg

4850 ms

img_lnk3.jpg

img_lnk3.jpg

5322 ms

logo.png

logo.png

5026 ms

ic_group.png

ic_group.png

5083 ms

logo_g2.png

logo_g2.png

5375 ms

ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZqFCjwA.ttf

ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZqFCjwA.ttf

41 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

9 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnTYo.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnTYo.ttf

42 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

56 ms

icomoon.ttf

icomoon.ttf

4938 ms

logo_g3.png

logo_g3.png

4847 ms

logo_g5.png

logo_g5.png

4876 ms

ic_group_cls.png

ic_group_cls.png

4811 ms

logo_g1.png

logo_g1.png

4778 ms

logo_g4.png

logo_g4.png

4769 ms

img_oth_lnk1.jpg

img_oth_lnk1.jpg

4769 ms

img_oth_lnk2.jpg

img_oth_lnk2.jpg

5017 ms

logo-pc.png

logo-pc.png

4701 ms

img_art6.jpg

img_art6.jpg

4883 ms

img_art7.jpg

img_art7.jpg

4700 ms

img_art8.jpg

img_art8.jpg

4738 ms

img_art11.jpg

img_art11.jpg

4908 ms

Accessibility Review

portom.jp accessibility score

83

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

portom.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

portom.jp SEO score

68

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

High

Document doesn't have a valid hreflang

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portom.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Portom.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

portom.jp

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