Tools & Wizards About Us
eatindiapalace.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

eatindiapalace.com

India Palace (Uptown) - South Minneapolis, MN 55405 (Menu & Order Online)

Page Load Speed

608 ms in total

First Response

41 ms

Resources Loaded

445 ms

Page Rendered

122 ms

eatindiapalace.com screenshot

About Website

Visit eatindiapalace.com now to see the best up-to-date Eat India Palace content and also check out these interesting facts you probably never knew about eatindiapalace.com

Online ordering menu for India Palace (Uptown). Whenever you're in South Minneapolis, India Palace is the go to place for traditional Indian cuisine. We have Vegetarian, Lamb, Balti, Beef, Seafood...

Visit eatindiapalace.com

Key Findings

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

Performance Metrics

eatindiapalace.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

84/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value1,570 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

eatindiapalace.com

41 ms

www.eatindiapalace.com

117 ms

all.min.css

39 ms

css2

42 ms

bootstrap.min.css

62 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Eatindiapalace.com, 67% (20 requests) were made to Production-cdn-hdb5b9fwgnb9bdf9.z01.azurefd.net and 10% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (117 ms) belongs to the original domain Eatindiapalace.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 166.6 kB (46%)

Content Size

358.5 kB

After Optimization

191.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eatindiapalace.com main page is 358.5 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. 55% of websites need less resources to load. HTML takes 151.7 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 135.3 kB

  • Original 151.7 kB
  • After minification 126.3 kB
  • After compression 16.4 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 25.4 kB, which is 17% 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 135.3 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 20.2 kB
  • After minification 20.2 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. Eat India Palace images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 21.2 kB

  • Original 137.8 kB
  • After minification 137.8 kB
  • After compression 116.6 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 21.2 kB or 15% of the original size.

CSS Optimization

-21%

Potential reduce by 10.1 kB

  • Original 48.8 kB
  • After minification 48.8 kB
  • After compression 38.7 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. Eatindiapalace.com needs all CSS files to be minified and compressed as it can save up to 10.1 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (59%)

Requests Now

22

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eatindiapalace.com

eatindiapalace.com

41 ms

www.eatindiapalace.com

www.eatindiapalace.com

117 ms

all.min.css

all.min.css

39 ms

css2

css2

42 ms

bootstrap.min.css

bootstrap.min.css

62 ms

website.min.css

website.min.css

49 ms

order.min.css

order.min.css

50 ms

bundle.min.js

bundle.min.js

51 ms

bundle.tracing.min.js

bundle.tracing.min.js

53 ms

en.js

en.js

51 ms

all.min.js

all.min.js

78 ms

js

js

100 ms

allOrder.min.js

allOrder.min.js

55 ms

mapkit.js

mapkit.js

31 ms

maps.min.js

maps.min.js

57 ms

analytics.min.js

analytics.min.js

56 ms

icon-vegetarian.svg

icon-vegetarian.svg

42 ms

icon-glutenfree.svg

icon-glutenfree.svg

47 ms

icon-spicy1x.svg

icon-spicy1x.svg

44 ms

icon-vegan.svg

icon-vegan.svg

45 ms

google_pay_mark.svg

google_pay_mark.svg

42 ms

blue_venmo_acceptance_mark.svg

blue_venmo_acceptance_mark.svg

44 ms

637922794601308513+853236.png

637922794601308513+853236.png

50 ms

script.js

script.js

55 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

49 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

57 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

63 ms

fa-solid-900.woff

fa-solid-900.woff

25 ms

fa-regular-400.woff

fa-regular-400.woff

9 ms

fa-brands-400.woff

fa-brands-400.woff

36 ms

Accessibility Review

eatindiapalace.com accessibility score

100

Accessibility Issues

Best Practices

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

eatindiapalace.com SEO score

99

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eatindiapalace.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Eatindiapalace.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

eatindiapalace.com

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