Tools & Wizards About Us
south-park.jp screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

south-park.jp

SOUTH PARK- South Indian Homely Cuisine from Kerala

Page Load Speed

4.1 sec in total

First Response

617 ms

Resources Loaded

3.1 sec

Page Rendered

435 ms

south-park.jp screenshot

About Website

Visit south-park.jp now to see the best up-to-date SOUTH PARK content for Japan and also check out these interesting facts you probably never knew about south-park.jp

South Park - A South Indian (Kerala) restaurant located at Asakusa and Ojima. We serve homely cuisine from Kerala.South Park is a place where you will experience the flavours of traditional homely Ker...

Visit south-park.jp

Key Findings

We analyzed South-park.jp page load time and found that the first response time was 617 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

south-park.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.879

3/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

south-park.jp

617 ms

css

35 ms

css

51 ms

css

57 ms

open-iconic-bootstrap.min.css

324 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 78% of them (50 requests) were addressed to the original South-park.jp, 16% (10 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain South-park.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (27%)

Content Size

4.0 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 48.2 kB

  • Original 54.1 kB
  • After minification 38.7 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 15.3 kB, which is 28% 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 48.2 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 88.8 kB

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

JavaScript Optimization

-62%

Potential reduce by 389.3 kB

  • Original 624.4 kB
  • After minification 597.7 kB
  • After compression 235.1 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 389.3 kB or 62% of the original size.

CSS Optimization

-89%

Potential reduce by 523.8 kB

  • Original 590.3 kB
  • After minification 454.1 kB
  • After compression 66.5 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. South-park.jp needs all CSS files to be minified and compressed as it can save up to 523.8 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (60%)

Requests Now

50

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SOUTH PARK. 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 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

south-park.jp

south-park.jp

617 ms

css

css

35 ms

css

css

51 ms

css

css

57 ms

open-iconic-bootstrap.min.css

open-iconic-bootstrap.min.css

324 ms

animate.css

animate.css

702 ms

owl.carousel.min.css

owl.carousel.min.css

378 ms

owl.theme.default.min.css

owl.theme.default.min.css

379 ms

magnific-popup.css

magnific-popup.css

399 ms

aos.css

aos.css

606 ms

ionicons.min.css

ionicons.min.css

488 ms

bootstrap-datepicker.css

bootstrap-datepicker.css

565 ms

jquery.timepicker.css

jquery.timepicker.css

569 ms

flaticon.css

flaticon.css

598 ms

icomoon.css

icomoon.css

813 ms

style.css

style.css

1502 ms

sp_logo_3.png

sp_logo_3.png

945 ms

blank.gif

blank.gif

796 ms

jquery.min.js

jquery.min.js

1458 ms

jquery-migrate-3.0.1.min.js

jquery-migrate-3.0.1.min.js

718 ms

popper.min.js

popper.min.js

840 ms

bootstrap.min.js

bootstrap.min.js

821 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

893 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

980 ms

jquery.stellar.min.js

jquery.stellar.min.js

986 ms

owl.carousel.min.js

owl.carousel.min.js

1238 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1078 ms

aos.js

aos.js

1170 ms

jquery.animateNumber.min.js

jquery.animateNumber.min.js

1149 ms

bootstrap-datepicker.js

bootstrap-datepicker.js

1253 ms

jquery.timepicker.min.js

jquery.timepicker.min.js

1314 ms

scrollax.min.js

scrollax.min.js

1442 ms

js

js

57 ms

google-map.js

google-map.js

1442 ms

main.js

main.js

1442 ms

flags.png

flags.png

266 ms

d8c6c3a5-4b51-4f2b-ba94-8f9602790ade.jpg

d8c6c3a5-4b51-4f2b-ba94-8f9602790ade.jpg

642 ms

5c2444be-4fa4-454f-8634-36e13124d2f2.jpg

5c2444be-4fa4-454f-8634-36e13124d2f2.jpg

266 ms

a639505d-53fa-4caa-b7e3-05b5992eb81f.jpg

a639505d-53fa-4caa-b7e3-05b5992eb81f.jpg

764 ms

leaf.jpg

leaf.jpg

673 ms

spbg.jpg

spbg.jpg

312 ms

thumb1.jpg

thumb1.jpg

431 ms

thumb2.jpg

thumb2.jpg

454 ms

thumb3.jpg

thumb3.jpg

506 ms

thumb4.jpg

thumb4.jpg

595 ms

thumb5.jpg

thumb5.jpg

643 ms

pxiByp8kv8JHgFVrLBT5Z1xlEw.woff

pxiByp8kv8JHgFVrLBT5Z1xlEw.woff

155 ms

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

185 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

198 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

199 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

200 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

199 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

198 ms

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

200 ms

pxiGyp8kv8JHgFVrLPTucHtG.woff

pxiGyp8kv8JHgFVrLPTucHtG.woff

200 ms

E21-_dn5gvrawDdPFVl-N0Ajb_qoUvE.woff

E21-_dn5gvrawDdPFVl-N0Ajb_qoUvE.woff

232 ms

ionicons.woff

ionicons.woff

629 ms

icomoon.ttf

icomoon.ttf

841 ms

Flaticon.svg

Flaticon.svg

751 ms

Flaticon.woff

Flaticon.woff

764 ms

slide1.jpg

slide1.jpg

837 ms

slide6.jpg

slide6.jpg

680 ms

slide1-1.jpg

slide1-1.jpg

709 ms

spreview.jpg

spreview.jpg

787 ms

Accessibility Review

south-park.jp accessibility score

87

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

south-park.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

south-park.jp SEO score

98

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

south-park.jp

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