Tools & Wizards About Us
pekingtokyony.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

pekingtokyony.com

Peking Tokyo

Page Load Speed

1.4 sec in total

First Response

51 ms

Resources Loaded

463 ms

Page Rendered

930 ms

pekingtokyony.com screenshot

About Website

Welcome to pekingtokyony.com homepage info - get ready to check Peking Tokyo Ny best content right away, or after learning these important things about pekingtokyony.com

Peking Tokyo Online Order - 3 Henderson ST(UNIT3), NEW YORK MILLS, NY 13417

Visit pekingtokyony.com

Key Findings

We analyzed Pekingtokyony.com page load time and found that the first response time was 51 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

pekingtokyony.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

pekingtokyony.com

51 ms

pekingtokyony.com

31 ms

css

65 ms

bootstrap.min.css

12 ms

font-awesome.min.css

31 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 75% of them (45 requests) were addressed to the original Pekingtokyony.com, 17% (10 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fbgcdn.com. The less responsive or slowest element that took the longest time to load (346 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 288.7 kB (5%)

Content Size

6.1 MB

After Optimization

5.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pekingtokyony.com main page is 6.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. 80% 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.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 22.5 kB

  • Original 26.9 kB
  • After minification 18.9 kB
  • After compression 4.3 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 7.9 kB, which is 30% 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 22.5 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 169.3 kB

  • Original 5.8 MB
  • After minification 5.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. Peking Tokyo Ny images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 89.8 kB

  • Original 208.5 kB
  • After minification 175.3 kB
  • After compression 118.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 89.8 kB or 43% of the original size.

CSS Optimization

-15%

Potential reduce by 7.0 kB

  • Original 47.5 kB
  • After minification 46.2 kB
  • After compression 40.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. Pekingtokyony.com needs all CSS files to be minified and compressed as it can save up to 7.0 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (53%)

Requests Now

47

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pekingtokyony.com

pekingtokyony.com

51 ms

pekingtokyony.com

pekingtokyony.com

31 ms

css

css

65 ms

bootstrap.min.css

bootstrap.min.css

12 ms

font-awesome.min.css

font-awesome.min.css

31 ms

pe-icon-7-stroke.css

pe-icon-7-stroke.css

33 ms

flaticon.css

flaticon.css

31 ms

owl.carousel.css

owl.carousel.css

35 ms

swiper.css

swiper.css

34 ms

magnific-popup.css

magnific-popup.css

36 ms

slicknav.css

slicknav.css

42 ms

ewm2.js

ewm2.js

54 ms

CSTiles-1.1.0.css

CSTiles-1.1.0.css

41 ms

custom.css

custom.css

40 ms

style.css

style.css

42 ms

logo.png

logo.png

43 ms

embed

embed

346 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

44 ms

SmoothScroll.js

SmoothScroll.js

45 ms

bootstrap.min.js

bootstrap.min.js

47 ms

jquery.counterup.min.js

jquery.counterup.min.js

42 ms

jquery.slicknav.js

jquery.slicknav.js

45 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

46 ms

owl.carousel.js

owl.carousel.js

47 ms

jquery.CSTiles-1.1.0.min.js

jquery.CSTiles-1.1.0.min.js

46 ms

function.js

function.js

47 ms

swiper.min.js

swiper.min.js

55 ms

contact_me.js

contact_me.js

49 ms

jqBootstrapValidation.js

jqBootstrapValidation.js

52 ms

1.png

1.png

216 ms

2.jpg

2.jpg

219 ms

2.jpg

2.jpg

57 ms

3.jpg

3.jpg

215 ms

5.jpg

5.jpg

220 ms

6.jpg

6.jpg

226 ms

4.jpeg

4.jpeg

218 ms

8.jpg

8.jpg

228 ms

5.jpg

5.jpg

221 ms

6.jpg

6.jpg

221 ms

11.jpg

11.jpg

222 ms

contact.png

contact.png

223 ms

close.png

close.png

213 ms

order-online.css

order-online.css

42 ms

1.jpg

1.jpg

40 ms

2.jpg

2.jpg

48 ms

history-bg.jpg

history-bg.jpg

39 ms

services-bg.png

services-bg.png

24 ms

services-cup.png

services-cup.png

40 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

47 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

49 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

78 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

81 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff

84 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff

80 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff

82 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff

78 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtU.woff

81 ms

Pe-icon-7-stroke.woff

Pe-icon-7-stroke.woff

20 ms

js

js

35 ms

Accessibility Review

pekingtokyony.com accessibility score

93

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

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

High

Links do not have a discernible name

Best Practices

pekingtokyony.com 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

High

Page has valid source maps

SEO Factors

pekingtokyony.com SEO score

100

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

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 Pekingtokyony.com 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 Pekingtokyony.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

pekingtokyony.com

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