3.5 sec in total
13 ms
3.1 sec
416 ms
Welcome to city-spice.london homepage info - get ready to check City Spice best content right away, or after learning these important things about city-spice.london
Welcome to City Spice, the ultimate curry house in London's Brick Lane. Enjoy authentic Indian cuisine with a modern twist. Book a table now!
Visit city-spice.londonWe analyzed City-spice.london page load time and found that the first response time was 13 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.
city-spice.london performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value15.4 s
0/100
25%
Value11.7 s
4/100
10%
Value3,640 ms
1/100
30%
Value0.044
99/100
15%
Value16.8 s
5/100
10%
13 ms
321 ms
614 ms
191 ms
275 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original City-spice.london, 78% (72 requests) were made to Cityspice.co and 11% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Cityspice.co.
Page size can be reduced by 114.9 kB (11%)
1.0 MB
932.4 kB
In fact, the total size of City-spice.london main page is 1.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. 65% of websites need less resources to load. Javascripts take 734.8 kB which makes up the majority of the site volume.
Potential reduce by 106.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. 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 106.9 kB or 82% of the original size.
Potential reduce by 1.4 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. Obviously, City Spice needs image optimization as it can save up to 1.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 4.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.0 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. City-spice.london has all CSS files already compressed.
Number of requests can be reduced by 72 (92%)
78
6
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of City Spice. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
city-spice.london
13 ms
www.cityspice.co
321 ms
cityspice.co
614 ms
1692916582-css2a64689c27a5c7ecabf25184af5388afaa35b522081036f2e174229590982.css
191 ms
1692916582-css621ac1a528864c73495872c969abd8f6ee1350ac4bf7ec915190657a2f0e0.css
275 ms
1692916582-css6865e7d38ac8bc6d17e6b65180eeb8fdabc8e2c843847b8c56e1e04a70e0f.css
276 ms
1692916582-cssb4163f68a317da780aae9dff6b0a3a7d81fce09c3ebe613e19718395550e6.css
278 ms
1692916582-css952451415b394160862deb7e64b07ec3dd3d58c27c53450a9f70dd144a155.css
274 ms
1692916582-css308619cfae337bbb7774b91106b901b8c487ed0dd7a22993689717b32c6a0.css
282 ms
1692916582-css8b850d3709fa17d878443b09e33340d5497b636e2d376c3c6578fc44ddd84.css
762 ms
1692916582-css90d5b38c74068c250fb053695fdde116f35cdfd8870d8e66eb88a12e9b677.css
365 ms
1692916582-css6e563c45aaf647f3cd2a8ce75471eb8a369585c18a67888c1aeeb73e75889.css
367 ms
1692916582-css9a8de7519ef69fa5cea09fe9567ffc933133aca9099d6e3d47fad879a22f3.css
368 ms
1692916582-css0349f2d65217584622026f987590105c9db7063e44b5eaebbb8c4a28ecb6b.css
372 ms
1692916582-css4da004465f4db1147f1d33e64d0e3a8acbcb2c6f25624740edb1fe0dae98a.css
376 ms
1692916582-cssdf0eaede3c1278571b07d29b3f416d370f4c583b744066253780f155aafde.css
454 ms
1692916582-cssf15e86d7c72fca8ccc203fdc4ebbe609372b5dbc6e272b55a89282b4c26c2.css
456 ms
1692916582-csse2c7dd0c191c6d69611a1f11c49d8b3b9eaa69fe334574ccb1c1c738a68fa.css
457 ms
1692916582-cssde99ca8ce389405a06b35517a299fe4146447f2dde7666526cdc737f53734.css
457 ms
1692916582-css81f96d0c8f00608dda8760326f8f82fc870427c6faaabc7b211e569c8352f.css
470 ms
1692916582-cssa7a53353c0622972382edfbbdc0cc2c57c092a1648da8dcdc66bca062af06.css
546 ms
1692916582-csscfb6b114c3a45de3b9fa394f52bb0d4873a7e0082ab59301f4b76c160343b.css
546 ms
1692916582-cssb1b9a8ef76544479d4ee0186f37eff3dfd9228e729b647aa01c820b0d85cd.css
556 ms
jquery.min.js
550 ms
jquery-migrate.min.js
578 ms
rbtools.min.js
1003 ms
rs6.min.js
823 ms
js
65 ms
js
118 ms
1692916582-cssde22aaee10c9be4ad419936163c0fc1881101308d1d66b63e3ce54664b2b6.css
640 ms
1692916582-cssb871de5084a2dc730255141d7e5249377d2efe2534b89ebe12d7ecee19a2d.css
645 ms
360-view.js
657 ms
index.js
731 ms
index.js
737 ms
core.min.js
845 ms
tabs.min.js
821 ms
accordion.min.js
827 ms
datepicker.min.js
945 ms
mediaelement-and-player.min.js
918 ms
mediaelement-migrate.min.js
911 ms
js
69 ms
api.js
52 ms
wp-mediaelement.min.js
917 ms
jquery.appear.js
755 ms
modernizr.min.js
825 ms
hoverIntent.min.js
823 ms
jquery.plugin.js
823 ms
owl.carousel.min.js
905 ms
jquery.waypoints.min.js
819 ms
fluidvids.min.js
734 ms
jquery.prettyPhoto.min.js
812 ms
perfect-scrollbar.jquery.min.js
811 ms
ScrollToPlugin.min.js
810 ms
parallax.min.js
808 ms
jquery.waitforimages.js
787 ms
jquery.easing.1.3.js
818 ms
isotope.pkgd.min.js
815 ms
packery-mode.pkgd.min.js
814 ms
jquery.geocomplete.min.js
804 ms
jquery.countdown.min.js
727 ms
counter.js
757 ms
absoluteCounter.min.js
955 ms
typed.js
930 ms
jquery.fullPage.min.js
928 ms
easypiechart.js
869 ms
modules.min.js
858 ms
dflip.min.js
904 ms
wp-polyfill-inert.min.js
892 ms
regenerator-runtime.min.js
888 ms
wp-polyfill.min.js
906 ms
index.js
804 ms
smush-lazy-load-native.min.js
805 ms
js_composer_front.min.js
869 ms
vc-waypoints.min.js
926 ms
transparent.png
732 ms
js
206 ms
analytics.js
199 ms
KFOmCnqEu92Fr1Mu7GxM.woff
200 ms
KFOlCnqEu92Fr1MmEU9fChc-.woff
201 ms
KFOlCnqEu92Fr1MmSU5fChc-.woff
302 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
352 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYw.woff
356 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYw.woff
355 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYw.woff
357 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYw.woff
357 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYw.woff
354 ms
ElegantIcons.woff
570 ms
KFOmCnqEu92Fr1Mu4mxM.woff
142 ms
collect
108 ms
collect
139 ms
recaptcha__en.js
62 ms
City-Spice-1.png
269 ms
city-spice.london accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
city-spice.london best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
city-spice.london SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise City-spice.london 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 City-spice.london 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.
city-spice.london
Open Graph data is detected on the main page of City Spice. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: