3.4 sec in total
249 ms
2.6 sec
573 ms
Click here to check amazing I Local content for Switzerland. Otherwise, check out these important facts you probably never knew about i.local.ch
Find more than 500,000 shops
Visit i.local.chWe analyzed I.local.ch page load time and found that the first response time was 249 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
i.local.ch performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value11.9 s
0/100
25%
Value6.9 s
33/100
10%
Value2,330 ms
5/100
30%
Value0
100/100
15%
Value11.9 s
17/100
10%
249 ms
527 ms
210 ms
49 ms
106 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original I.local.ch, 95% (58 requests) were made to Local.ch and 2% (1 request) were made to Bshxwih1dv.kameleoon.eu. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Local.ch.
Page size can be reduced by 78.9 kB (52%)
152.3 kB
73.4 kB
In fact, the total size of I.local.ch main page is 152.3 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. 40% of websites need less resources to load. HTML takes 100.9 kB which makes up the majority of the site volume.
Potential reduce by 77.8 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 77.8 kB or 77% of the original size.
Potential reduce by 1.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. Obviously, I Local needs image optimization as it can save up to 1.1 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 0 B
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.
Number of requests can be reduced by 31 (53%)
58
27
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I Local. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
i.local.ch
249 ms
www.local.ch
527 ms
en
210 ms
kameleoon.js
49 ms
gtm.js
106 ms
b017f3fb4a1337c2.css
291 ms
f3fe51e25e505ec3.css
305 ms
54b59211ffffe50d.css
389 ms
d18517aad9fa314b.css
402 ms
polyfills-c67a75d1b6f99dc8.js
502 ms
3187.2c3536bf1a204a75.js
466 ms
6241-54e228f88d03efdf.js
465 ms
3718-4780ab099c664a12.js
602 ms
1417.efc9436830481854.js
487 ms
webpack-ad2bb9e24fe6dae3.js
499 ms
framework-44b956e964c65a62.js
601 ms
main-0103424299deef85.js
698 ms
_app-89995f98a33c0b4e.js
879 ms
0c8590f2-3fac8c0330bcdc67.js
595 ms
11ef7cab-3428f5a251ba151d.js
600 ms
a97078f4-fd0a849d238c0a26.js
692 ms
abdb7d0b-e16fd7def1f76dc2.js
700 ms
2087-391b548a3b2cbeb9.js
700 ms
7955-754df822aa65e647.js
699 ms
1926-56a23cd2df234908.js
790 ms
5618-fd5cf5279c5e3831.js
795 ms
5812-4ec1c03f8c266355.js
797 ms
2803-95ad37e0aebc6a63.js
797 ms
2977-92c795ce5c9c8694.js
797 ms
2481-cb4e14991cc8cdea.js
1080 ms
8164-94ec02d8f2b5fb99.js
894 ms
554-f62b7f0554bac1f2.js
898 ms
5617-be14efa4bffcbd83.js
897 ms
index-460eb1382f7689a6.js
897 ms
_buildManifest.js
973 ms
_ssgManifest.js
992 ms
restaurants.webp
914 ms
hotels.webp
911 ms
garages.webp
913 ms
bars.webp
988 ms
hairdressers.webp
1005 ms
zurich.webp
811 ms
geneva.webp
808 ms
lausanne.webp
723 ms
bern.webp
725 ms
sion.webp
722 ms
basel.webp
946 ms
lucerne.webp
734 ms
default.webp
719 ms
fribourg.webp
697 ms
bielbienne.webp
693 ms
lugano.webp
689 ms
neuchatel.webp
720 ms
nyon.webp
713 ms
st-gallen.webp
630 ms
winterthur.webp
692 ms
thun.webp
692 ms
chur.webp
721 ms
bellinzona.webp
723 ms
swissmade_batch_72dpi_RGB.png
635 ms
1920x1080.9746e945.webp
884 ms
i.local.ch 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.
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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
i.local.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
i.local.ch 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
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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I.local.ch 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 I.local.ch 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.
i.local.ch
Open Graph data is detected on the main page of I Local. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: