Tools & Wizards About Us
pekingalley.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

pekingalley.com

Peking Alley-Chinese Restaurant | Online Order | San Mateo | CA

Page Load Speed

2.2 sec in total

First Response

141 ms

Resources Loaded

1.7 sec

Page Rendered

341 ms

pekingalley.com screenshot

About Website

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

Visit pekingalley.com

Key Findings

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

Performance Metrics

pekingalley.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

pekingalley.com

141 ms

www.pekingalley.com

347 ms

style.min.css

128 ms

magnific_popup.css

190 ms

swiper.css

191 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 48% of them (35 requests) were addressed to the original Pekingalley.com, 38% (28 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (406 ms) belongs to the original domain Pekingalley.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 357.8 kB (47%)

Content Size

764.4 kB

After Optimization

406.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pekingalley.com main page is 764.4 kB. 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. Javascripts take 385.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 159.0 kB

  • Original 187.7 kB
  • After minification 182.0 kB
  • After compression 28.7 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 159.0 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 1.6 kB

  • Original 104.7 kB
  • After minification 103.1 kB

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 Alley images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 174.2 kB

  • Original 385.6 kB
  • After minification 385.6 kB
  • After compression 211.4 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 174.2 kB or 45% of the original size.

CSS Optimization

-27%

Potential reduce by 23.1 kB

  • Original 86.4 kB
  • After minification 86.4 kB
  • After compression 63.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. Pekingalley.com needs all CSS files to be minified and compressed as it can save up to 23.1 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (50%)

Requests Now

42

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pekingalley.com

pekingalley.com

141 ms

www.pekingalley.com

www.pekingalley.com

347 ms

style.min.css

style.min.css

128 ms

magnific_popup.css

magnific_popup.css

190 ms

swiper.css

swiper.css

191 ms

popup.css

popup.css

204 ms

animate.css

animate.css

206 ms

readmore.css

readmore.css

205 ms

js

js

48 ms

jquery.min.js

jquery.min.js

284 ms

jquery-migrate.min.js

jquery-migrate.min.js

283 ms

scripts.min.js

scripts.min.js

381 ms

smoothscroll.js

smoothscroll.js

282 ms

jquery.fitvids.js

jquery.fitvids.js

282 ms

common.js

common.js

283 ms

magnific-popup.js

magnific-popup.js

314 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

337 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

337 ms

frontend.min.js

frontend.min.js

338 ms

gtm.js

gtm.js

31 ms

place

place

327 ms

logo.jpg

logo.jpg

129 ms

10013.jpg

10013.jpg

283 ms

10012.jpg

10012.jpg

284 ms

10010.jpg

10010.jpg

284 ms

10009.jpg

10009.jpg

284 ms

10008.jpg

10008.jpg

271 ms

10007.jpg

10007.jpg

284 ms

10006.jpg

10006.jpg

341 ms

10005.jpg

10005.jpg

340 ms

10004.jpg

10004.jpg

404 ms

10003.jpg

10003.jpg

403 ms

10002.jpg

10002.jpg

404 ms

10001.jpg

10001.jpg

406 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

23 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

26 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

25 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

26 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

26 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

25 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

38 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff

38 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

40 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

41 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

42 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff

41 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

41 ms

modules.ttf

modules.ttf

325 ms

Sample+Background+Image+2.png

Sample+Background+Image+2.png

93 ms

Sample+Background+Image+3.png

Sample+Background+Image+3.png

47 ms

Sample+Background+Image+4.png

Sample+Background+Image+4.png

48 ms

banner.jpg

banner.jpg

166 ms

logo.jpg

logo.jpg

220 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQEl5fsA-O.woff

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQEl5fsA-O.woff

26 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQEl5fsA-N.ttf

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQEl5fsA-N.ttf

25 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQdl9fsA-O.woff

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQdl9fsA-O.woff

26 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQdl9fsA-N.ttf

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQdl9fsA-N.ttf

25 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQWlhfsA-O.woff

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQWlhfsA-O.woff

22 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQWlhfsA-N.ttf

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQWlhfsA-N.ttf

25 ms

co3bmX5slCNuHLi8bLeY9MK7whWMhyjYp3tM.woff

co3bmX5slCNuHLi8bLeY9MK7whWMhyjYp3tM.woff

41 ms

co3bmX5slCNuHLi8bLeY9MK7whWMhyjYp3tP.ttf

co3bmX5slCNuHLi8bLeY9MK7whWMhyjYp3tP.ttf

40 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQAllfsA-O.woff

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQAllfsA-O.woff

40 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQAllfsA-N.ttf

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQAllfsA-N.ttf

40 ms

js

js

27 ms

search.js

search.js

3 ms

geometry.js

geometry.js

6 ms

main.js

main.js

12 ms

style.min.css

style.min.css

65 ms

Accessibility Review

pekingalley.com accessibility score

95

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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

pekingalley.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

pekingalley.com SEO score

93

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

pekingalley.com

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