Access intex-osaka.com. 日本最大級の国際展示場インテックス大阪

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value8,280 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value28.9 s

0/100

10%

intex-osaka.com

566 ms

426 ms

gtm.js

66 ms

common.css

542 ms

css

43 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 56% of them (59 requests) were addressed to the original Intex-osaka.com, 17% (18 requests) were made to Platform.twitter.com and 11% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Intex-osaka.com.

Content Size

5.7 MB

After Optimization

5.3 MB

In fact, the total size of Intex-osaka.com main page is 5.7 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. 75% 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 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 105.8 kB

Original 119.3 kB
After minification 94.7 kB
After compression 13.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 24.6 kB, which is 21% 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 105.8 kB or 89% of the original size.

Image Optimization

-5%

Potential reduce by 281.5 kB

Original 5.4 MB
After minification 5.2 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. Intex Osaka images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 19.4 kB

Original 99.2 kB
After minification 99.2 kB
After compression 79.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 19.4 kB or 20% of the original size.

CSS Optimization

-26%

Potential reduce by 11.2 kB

Original 42.4 kB
After minification 42.4 kB
After compression 31.2 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. Intex-osaka.com needs all CSS files to be minified and compressed as it can save up to 11.2 kB or 26% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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

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

High

Image elements do not have [alt] attributes

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

High

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

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links are not crawlable

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

JA
Encoding

UTF-8

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

intex-osaka.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

日本最大級の国際展示場 インテックス大阪

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

intex-osaka.com

gtm.js

common.css

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

intex-osaka.com

gtm.js

common.css

css

style.css

slick.css

main_logo.png

main.jpg

main_sp.jpg

main_copy_a@2x.png

bunner_chiwan.jpg

robot2024.jpg

ad_detail.jpg

restaurant1018.jpg

kyoiku2024.jpg

js

analytics.js

collect

embed

page.php

widgets.js

jquery-3.2.1.min.js

ofi.min.js

stickyfill.min.js

lazysizes.min.js

jquery.inview.min.js

app_rsp.js

common.js

slick.min.js

script.js

bouhanbousai2024.jpg

anzen_banner1.jpg

intex_plaza.jpg

icon_map.png

icon_restaurant.png

icon_toilet.png

icon_coin.png

icon_baby.png

icon_service.png

icon_parking.png

icon_guide.png

benner_miceexpo.jpg

banner_zhejiang.jpg

event_illust.png

日本最大級の国際展示場インテックス大阪