Tools & Wizards About Us
in-section.com screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

in-section.com

大阪飲食店グループ インターセクション

Page Load Speed

7.1 sec in total

First Response

2.2 sec

Resources Loaded

4.7 sec

Page Rendered

192 ms

in-section.com screenshot

About Website

Visit in-section.com now to see the best up-to-date In Section content for Japan and also check out these interesting facts you probably never knew about in-section.com

大阪の飲食店グループ、インターセクションのウェブサイト。バー、和食、居酒屋からイタリアン、焼肉店など大阪府下に続々と展開中。一店舗一店舗の個性とクオリティを重視したトータルプランニングを行っております。

Visit in-section.com

Key Findings

We analyzed In-section.com page load time and found that the first response time was 2.2 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

in-section.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

in-section.com

2242 ms

main.css

185 ms

jquery-1.3.2.min.js

528 ms

slider.js

354 ms

jquery.cross-slide.js

357 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 96% of them (44 requests) were addressed to the original In-section.com, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain In-section.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.3 kB (1%)

Content Size

1.9 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of In-section.com main page is 1.9 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. 30% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 6.7 kB

  • Original 9.5 kB
  • After minification 9.5 kB
  • After compression 2.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 6.7 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 935 B

  • Original 1.9 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. In Section images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 15.4 kB

  • Original 58.3 kB
  • After minification 53.5 kB
  • After compression 42.9 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 15.4 kB or 26% of the original size.

CSS Optimization

-20%

Potential reduce by 284 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 1.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. In-section.com needs all CSS files to be minified and compressed as it can save up to 284 B or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (14%)

Requests Now

44

After Optimization

38

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

in-section.com

in-section.com

2242 ms

main.css

main.css

185 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

528 ms

slider.js

slider.js

354 ms

jquery.cross-slide.js

jquery.cross-slide.js

357 ms

iepngfix.js

iepngfix.js

368 ms

analytics.js

analytics.js

405 ms

discript.js

discript.js

419 ms

ga.js

ga.js

55 ms

header_bg2.gif

header_bg2.gif

180 ms

logo_2.gif

logo_2.gif

179 ms

loading.gif

loading.gif

178 ms

tag_news.gif

tag_news.gif

218 ms

party_2011.jpg

party_2011.jpg

587 ms

tag_apparatus.gif

tag_apparatus.gif

179 ms

tag_list.gif

tag_list.gif

364 ms

tag_prf.gif

tag_prf.gif

363 ms

tag_recruit.gif

tag_recruit.gif

355 ms

pager.png

pager.png

380 ms

liner_a.gif

liner_a.gif

365 ms

bg_shop.jpg

bg_shop.jpg

484 ms

kaburaya.jpg

kaburaya.jpg

672 ms

giocare.jpg

giocare.jpg

507 ms

heavens.jpg

heavens.jpg

685 ms

chrono.jpg

chrono.jpg

753 ms

muddy.jpg

muddy.jpg

838 ms

rokkan.jpg

rokkan.jpg

683 ms

hodohodo.jpg

hodohodo.jpg

725 ms

honobono.jpg

honobono.jpg

859 ms

seigoin.jpg

seigoin.jpg

861 ms

hanare.jpg

hanare.jpg

888 ms

tanagokoro.jpg

tanagokoro.jpg

924 ms

ico_a.gif

ico_a.gif

979 ms

bg_footer.gif

bg_footer.gif

1022 ms

s_12.jpg

s_12.jpg

1217 ms

s_11.jpg

s_11.jpg

1217 ms

s_10.jpg

s_10.jpg

1245 ms

s_1.jpg

s_1.jpg

1484 ms

s_6.jpg

s_6.jpg

1815 ms

s_4.jpg

s_4.jpg

1575 ms

s_9.jpg

s_9.jpg

1584 ms

s_8.jpg

s_8.jpg

1581 ms

s_5.jpg

s_5.jpg

1442 ms

s_2.jpg

s_2.jpg

1627 ms

s_7.jpg

s_7.jpg

1675 ms

__utm.gif

__utm.gif

12 ms

Accessibility Review

in-section.com accessibility score

75

Accessibility Issues

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

Links do not have a discernible name

Best Practices

in-section.com best practices score

58

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

Browser errors were logged to the console

SEO Factors

in-section.com SEO score

67

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

Image elements do not have [alt] attributes

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 In-section.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 In-section.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

in-section.com

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