Tools & Wizards About Us
lokris.net screenshot

Report Summary

  • 0

    Performance

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

lokris.net

LOKRIS : services informatiques pour professionnels sur la région lyonnaise

Page Load Speed

6.4 sec in total

First Response

189 ms

Resources Loaded

5.6 sec

Page Rendered

586 ms

lokris.net screenshot

About Website

Visit lokris.net now to see the best up-to-date LOKRIS content and also check out these interesting facts you probably never knew about lokris.net

Mise en place / maintenance / dépannage de parcs informatiques. Développement web de sites vitrines, applications sur-mesure et applications mobiles.

Visit lokris.net

Key Findings

We analyzed Lokris.net page load time and found that the first response time was 189 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

lokris.net performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

lokris.net

189 ms

lokris.net

369 ms

bootstrap.min.css

246 ms

global.min.css

327 ms

google-maps.min.css

244 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 95% of them (90 requests) were addressed to the original Lokris.net, 2% (2 requests) were made to Google.com and 1% (1 request) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Lokris.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 374.7 kB (9%)

Content Size

4.2 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lokris.net 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. 45% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 41.1 kB

  • Original 48.7 kB
  • After minification 40.7 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 8.0 kB, which is 16% 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 41.1 kB or 84% of the original size.

Image Optimization

-9%

Potential reduce by 323.1 kB

  • Original 3.7 MB
  • After minification 3.4 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. LOKRIS images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 6.0 kB

  • Original 389.6 kB
  • After minification 389.6 kB
  • After compression 383.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 4.5 kB

  • Original 63.8 kB
  • After minification 63.8 kB
  • After compression 59.2 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. Lokris.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 49 (54%)

Requests Now

90

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lokris.net

lokris.net

189 ms

lokris.net

lokris.net

369 ms

bootstrap.min.css

bootstrap.min.css

246 ms

global.min.css

global.min.css

327 ms

google-maps.min.css

google-maps.min.css

244 ms

typo.min.css

typo.min.css

247 ms

colorbox.css

colorbox.css

249 ms

jquery.background-video.css

jquery.background-video.css

250 ms

page-nav.min.css

page-nav.min.css

480 ms

slider.min.css

slider.min.css

481 ms

tooltips.min.css

tooltips.min.css

483 ms

counters.min.css

counters.min.css

489 ms

social.min.css

social.min.css

500 ms

portfolio.min.css

portfolio.min.css

581 ms

pi.settings.css

pi.settings.css

724 ms

fontello.css

fontello.css

727 ms

font-awesome.min.css

font-awesome.min.css

732 ms

lokris.css

lokris.css

731 ms

cookieconsent.css

cookieconsent.css

744 ms

logo-base.png

logo-base.png

868 ms

4-professional-logo.png

4-professional-logo.png

1033 ms

hp.png

hp.png

959 ms

iiyama.png

iiyama.png

961 ms

VCSP_registered_color_with_border_rgb.png

VCSP_registered_color_with_border_rgb.png

1045 ms

veeam.jpg

veeam.jpg

1135 ms

VMSP_Saas.png

VMSP_Saas.png

1193 ms

VMTSP_SaaS.png

VMTSP_SaaS.png

1283 ms

wazo-original.png

wazo-original.png

1211 ms

baptiste.jpg

baptiste.jpg

1372 ms

jonathan.png

jonathan.png

1729 ms

johan.png

johan.png

2054 ms

api.js

api.js

45 ms

recaptcha.css

recaptcha.css

1430 ms

js

js

78 ms

api.js

api.js

72 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

25 ms

bootstrap.min.js

bootstrap.min.js

1487 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

1560 ms

gauge.min.js

gauge.min.js

1642 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1751 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1814 ms

pi.googleMapStyles.min.js

pi.googleMapStyles.min.js

1809 ms

jquery.gmap.min.js

jquery.gmap.min.js

1655 ms

requestAnimationFramePolyfill.min.js

requestAnimationFramePolyfill.min.js

1744 ms

jquery.placeholder.js

jquery.placeholder.js

1756 ms

jquery.scrollTo.min.js

jquery.scrollTo.min.js

1815 ms

jquery.background-video.js

jquery.background-video.js

1825 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

1804 ms

pi.init.scrollSpy.min.js

pi.init.scrollSpy.min.js

1745 ms

pi.global.min.js

pi.global.min.js

1773 ms

pi.slider.min.js

pi.slider.min.js

1814 ms

pi.init.slider.min.js

pi.init.slider.min.js

1820 ms

pi.tooltip.min.js

pi.tooltip.min.js

1810 ms

pi.init.tooltip.min.js

pi.init.tooltip.min.js

1794 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1743 ms

pi.counter.min.js

pi.counter.min.js

1761 ms

pi.init.counter.min.js

pi.init.counter.min.js

1809 ms

pi.parallax.min.js

pi.parallax.min.js

1819 ms

recaptcha__en.js

recaptcha__en.js

48 ms

pi.init.parallax.min.js

pi.init.parallax.min.js

1764 ms

pi.init.isotope.min.js

pi.init.isotope.min.js

1756 ms

pi.init.map.min.js

pi.init.map.min.js

1744 ms

pi.init.revolutionSlider.min.js

pi.init.revolutionSlider.min.js

1774 ms

cookieconsent.js

cookieconsent.js

1737 ms

app.js

app.js

1733 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1851 ms

fontello.woff

fontello.woff

1826 ms

aurore.jpg

aurore.jpg

1881 ms

theo_revelin.jpg

theo_revelin.jpg

1811 ms

voila_1704190278557.png

voila_1704190278557.png

1995 ms

voila_1664865677506.png

voila_1664865677506.png

1983 ms

clement.jpg

clement.jpg

1892 ms

johanB.jpg

johanB.jpg

1765 ms

gabi.jpg

gabi.jpg

1843 ms

damien.jpg

damien.jpg

1789 ms

maxime.jpg

maxime.jpg

1998 ms

voila_1692708559535.png

voila_1692708559535.png

2120 ms

clavel.png

clavel.png

1808 ms

logo_classcroute.png

logo_classcroute.png

1884 ms

logo_marchal.png

logo_marchal.png

1824 ms

nichrominox-logo.png

nichrominox-logo.png

1846 ms

logo_rtschapuis.png

logo_rtschapuis.png

1917 ms

logo_sodime.png

logo_sodime.png

2013 ms

aruba-0-18-245-100-1597131956.png

aruba-0-18-245-100-1597131956.png

2160 ms

LOGO_EBP_LOGICIEL-1.png

LOGO_EBP_LOGICIEL-1.png

1924 ms

logo_epp_Bronze_Center.png

logo_epp_Bronze_Center.png

1959 ms

fortinet.png

fortinet.png

1938 ms

mailinblack.png

mailinblack.png

1934 ms

ovh.png

ovh.png

1995 ms

ricoh-logo.png

ricoh-logo.png

2009 ms

wazo-original.png

wazo-original.png

2045 ms

teamviewer-icon200x200.png

teamviewer-icon200x200.png

2041 ms

hexagon.png

hexagon.png

1986 ms

overlay.png

overlay.png

1943 ms

clip.png

clip.png

2253 ms

Accessibility Review

lokris.net accessibility score

67

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lokris.net best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

lokris.net SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lokris.net can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lokris.net 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

lokris.net

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