Tools & Wizards About Us
sushirunner.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

sushirunner.com

Sushi Runner – Sushi Delivery Miami | Sushi Restaurant | Sushi Runner

Page Load Speed

3.4 sec in total

First Response

183 ms

Resources Loaded

2.9 sec

Page Rendered

272 ms

sushirunner.com screenshot

About Website

Welcome to sushirunner.com homepage info - get ready to check Sushi Runner best content for United States right away, or after learning these important things about sushirunner.com

Visit sushirunner.com

Key Findings

We analyzed Sushirunner.com page load time and found that the first response time was 183 ms and then it took 3.2 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

sushirunner.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

Network Requests Diagram

sushirunner.com

183 ms

sushirunner.com

1139 ms

styles.min.css

176 ms

main.min.css

182 ms

divi-builder.min.css

127 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 85% of them (108 requests) were addressed to the original Sushirunner.com, 7% (9 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Sushirunner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 597.4 kB (14%)

Content Size

4.2 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sushirunner.com main page is 4.2 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 218.9 kB

  • Original 258.5 kB
  • After minification 255.8 kB
  • After compression 39.6 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 218.9 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 37.9 kB

  • Original 2.3 MB
  • After minification 2.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. Sushi Runner images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 285.6 kB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 1.2 MB

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 285.6 kB or 19% of the original size.

CSS Optimization

-26%

Potential reduce by 54.9 kB

  • Original 210.3 kB
  • After minification 210.3 kB
  • After compression 155.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. Sushirunner.com needs all CSS files to be minified and compressed as it can save up to 54.9 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 98 (88%)

Requests Now

111

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sushirunner.com

sushirunner.com

183 ms

sushirunner.com

sushirunner.com

1139 ms

styles.min.css

styles.min.css

176 ms

main.min.css

main.min.css

182 ms

divi-builder.min.css

divi-builder.min.css

127 ms

style.min.css

style.min.css

184 ms

styles.css

styles.css

181 ms

contact-form-7-main.min.css

contact-form-7-main.min.css

188 ms

header-footer-elementor.css

header-footer-elementor.css

187 ms

frontend-lite.min.css

frontend-lite.min.css

252 ms

general.min.css

general.min.css

243 ms

eael-718.css

eael-718.css

245 ms

elementor-icons.min.css

elementor-icons.min.css

244 ms

swiper.min.css

swiper.min.css

247 ms

post-7.css

post-7.css

245 ms

frontend-lite.min.css

frontend-lite.min.css

305 ms

global.css

global.css

313 ms

post-718.css

post-718.css

309 ms

frontend.css

frontend.css

317 ms

post-12.css

post-12.css

308 ms

post-248.css

post-248.css

316 ms

style.min.css

style.min.css

374 ms

master-addons-styles.css

master-addons-styles.css

484 ms

css

css

39 ms

iconic-font.min.css

iconic-font.min.css

366 ms

fontawesome.min.css

fontawesome.min.css

377 ms

regular.min.css

regular.min.css

368 ms

jquery.min.js

jquery.min.js

427 ms

solid.min.css

solid.min.css

427 ms

brands.min.css

brands.min.css

429 ms

frontend.min.js

frontend.min.js

433 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

434 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

609 ms

wp-polyfill.min.js

wp-polyfill.min.js

613 ms

hooks.min.js

hooks.min.js

610 ms

i18n.min.js

i18n.min.js

611 ms

url.min.js

url.min.js

610 ms

api.js

api.js

35 ms

api-fetch.min.js

api-fetch.min.js

609 ms

react.min.js

react.min.js

524 ms

react-dom.min.js

react-dom.min.js

520 ms

dom-ready.min.js

dom-ready.min.js

516 ms

a11y.min.js

a11y.min.js

463 ms

blob.min.js

blob.min.js

462 ms

autop.min.js

autop.min.js

457 ms

block-serialization-default-parser.min.js

block-serialization-default-parser.min.js

464 ms

deprecated.min.js

deprecated.min.js

465 ms

dom.min.js

dom.min.js

409 ms

escape-html.min.js

escape-html.min.js

442 ms

element.min.js

element.min.js

452 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

453 ms

keycodes.min.js

keycodes.min.js

455 ms

priority-queue.min.js

priority-queue.min.js

443 ms

compose.min.js

compose.min.js

394 ms

private-apis.min.js

private-apis.min.js

439 ms

redux-routine.min.js

redux-routine.min.js

441 ms

data.min.js

data.min.js

447 ms

html-entities.min.js

html-entities.min.js

445 ms

shortcode.min.js

shortcode.min.js

441 ms

blocks.min.js

blocks.min.js

462 ms

moment.min.js

moment.min.js

438 ms

date.min.js

date.min.js

477 ms

primitives.min.js

primitives.min.js

439 ms

rich-text.min.js

rich-text.min.js

393 ms

warning.min.js

warning.min.js

393 ms

components.min.js

components.min.js

626 ms

keyboard-shortcuts.min.js

keyboard-shortcuts.min.js

445 ms

commands.min.js

commands.min.js

453 ms

notices.min.js

notices.min.js

274 ms

preferences-persistence.min.js

preferences-persistence.min.js

281 ms

preferences.min.js

preferences.min.js

307 ms

style-engine.min.js

style-engine.min.js

331 ms

token-list.min.js

token-list.min.js

336 ms

wordcount.min.js

wordcount.min.js

326 ms

block-editor.min.js

block-editor.min.js

455 ms

htcontactform-block.js

htcontactform-block.js

355 ms

index.js

index.js

379 ms

index.js

index.js

384 ms

general.min.js

general.min.js

386 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

18 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

27 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

38 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

44 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

38 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

45 ms

eael-718.js

eael-718.js

408 ms

scripts.min.js

scripts.min.js

499 ms

app.min.js

app.min.js

436 ms

common.js

common.js

440 ms

index.js

index.js

471 ms

plugins.js

plugins.js

434 ms

master-addons-scripts.js

master-addons-scripts.js

488 ms

frontend.js

frontend.js

486 ms

script.min.js

script.min.js

486 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

489 ms

webpack.runtime.min.js

webpack.runtime.min.js

493 ms

frontend-modules.min.js

frontend-modules.min.js

513 ms

frontend.min.js

frontend.min.js

509 ms

waypoints.min.js

waypoints.min.js

500 ms

core.min.js

core.min.js

501 ms

frontend.min.js

frontend.min.js

499 ms

elements-handlers.min.js

elements-handlers.min.js

453 ms

Raleway-VariableFont_wght.ttf

Raleway-VariableFont_wght.ttf

526 ms

Raleway-Black.ttf

Raleway-Black.ttf

513 ms

HomepageBaukasten-Bold.ttf

HomepageBaukasten-Bold.ttf

513 ms

Gotham-Narrow-Book.ttf

Gotham-Narrow-Book.ttf

538 ms

Myriad-Pro-Regular.ttf

Myriad-Pro-Regular.ttf

587 ms

symbols.svg

symbols.svg

454 ms

1-01-1.png

1-01-1.png

663 ms

img-15.webp

img-15.webp

483 ms

img-18-_1_-1024x827.webp

img-18-_1_-1024x827.webp

614 ms

img-16.webp

img-16.webp

543 ms

suchi-01-525x1024.webp

suchi-01-525x1024.webp

657 ms

img-17.png

img-17.png

516 ms

img-12.png

img-12.png

554 ms

img-13.png

img-13.png

560 ms

recaptcha__en.js

recaptcha__en.js

26 ms

anchor

anchor

58 ms

styles__ltr.css

styles__ltr.css

31 ms

recaptcha__en.js

recaptcha__en.js

33 ms

sr2BvsM2R_OZKHX83mSXJ8YBPDmTxOV2dVCuSpL6Gdo.js

sr2BvsM2R_OZKHX83mSXJ8YBPDmTxOV2dVCuSpL6Gdo.js

60 ms

webworker.js

webworker.js

58 ms

logo_48.png

logo_48.png

47 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

32 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

31 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

32 ms

recaptcha__en.js

recaptcha__en.js

35 ms

Accessibility Review

sushirunner.com accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

sushirunner.com best practices score

83

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

sushirunner.com SEO score

86

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 doesn't use 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 Sushirunner.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 Sushirunner.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

sushirunner.com

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