Tools & Wizards About Us
lighty.io screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

lighty.io

lighty.io - The Ultimate SDN Framework | Software Development Kit

Page Load Speed

19.9 sec in total

First Response

427 ms

Resources Loaded

19.2 sec

Page Rendered

237 ms

lighty.io screenshot

About Website

Visit lighty.io now to see the best up-to-date Lighty content for Slovakia and also check out these interesting facts you probably never knew about lighty.io

SDN Made Easy | Support, ease and accelerate the development of Software-Defined Networking solutions in Java, Python and Go.

Visit lighty.io

Key Findings

We analyzed Lighty.io page load time and found that the first response time was 427 ms and then it took 19.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

lighty.io performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

lighty.io

427 ms

lighty.io

587 ms

js

66 ms

dashicons.min.css

215 ms

all.min.css

428 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 81% of them (57 requests) were addressed to the original Lighty.io, 14% (10 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (9.2 sec) belongs to the original domain Lighty.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.4 kB (20%)

Content Size

496.5 kB

After Optimization

396.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lighty.io main page is 496.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. 65% of websites need less resources to load. CSS take 187.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 92.5 kB

  • Original 112.9 kB
  • After minification 109.1 kB
  • After compression 20.5 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 92.5 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 6.8 kB

  • Original 60.8 kB
  • After minification 54.0 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, Lighty needs image optimization as it can save up to 6.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 121 B

  • Original 135.0 kB
  • After minification 135.0 kB
  • After compression 134.9 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

-1%

Potential reduce by 981 B

  • Original 187.8 kB
  • After minification 187.8 kB
  • After compression 186.8 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. Lighty.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (76%)

Requests Now

50

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lighty.io

lighty.io

427 ms

lighty.io

lighty.io

587 ms

js

js

66 ms

dashicons.min.css

dashicons.min.css

215 ms

all.min.css

all.min.css

428 ms

extra.min.css

extra.min.css

323 ms

bootstrap.min.css

bootstrap.min.css

326 ms

font-sizes.min.css

font-sizes.min.css

414 ms

styles.css

styles.css

435 ms

clients-bar.css

clients-bar.css

437 ms

cookieblocker.min.css

cookieblocker.min.css

441 ms

style.min.css

style.min.css

555 ms

css

css

44 ms

elementor-icons.min.css

elementor-icons.min.css

513 ms

frontend.min.css

frontend.min.css

537 ms

swiper.min.css

swiper.min.css

550 ms

post-1430.css

post-1430.css

551 ms

global.css

global.css

551 ms

post-169.css

post-169.css

614 ms

enlighterjs.min.css

enlighterjs.min.css

644 ms

css

css

79 ms

fontawesome.min.css

fontawesome.min.css

647 ms

solid.min.css

solid.min.css

649 ms

regular.min.css

regular.min.css

652 ms

jquery.min.js

jquery.min.js

660 ms

jquery-migrate.min.js

jquery-migrate.min.js

715 ms

all.min.css

all.min.css

760 ms

v4-shims.min.css

v4-shims.min.css

759 ms

hooks.min.js

hooks.min.js

760 ms

i18n.min.js

i18n.min.js

761 ms

index.js

index.js

760 ms

index.js

index.js

761 ms

comment-reply.min.js

comment-reply.min.js

788 ms

bootstrap.min.js

bootstrap.min.js

789 ms

core.min.js

core.min.js

789 ms

script.min.js

script.min.js

790 ms

enlighterjs.min.js

enlighterjs.min.js

790 ms

complianz.min.js

complianz.min.js

827 ms

webpack.runtime.min.js

webpack.runtime.min.js

881 ms

frontend-modules.min.js

frontend-modules.min.js

882 ms

waypoints.min.js

waypoints.min.js

883 ms

frontend.min.js

frontend.min.js

778 ms

cropped-Asset-1.png

cropped-Asset-1.png

244 ms

pt-male.png

pt-male.png

279 ms

lighty-diagram-1-300x229.png

lighty-diagram-1-300x229.png

331 ms

lighty-by-pantheon1.png

lighty-by-pantheon1.png

370 ms

L-com-6-e1580720637807.png

L-com-6-e1580720637807.png

347 ms

L-com-7-e1580720674961.png

L-com-7-e1580720674961.png

348 ms

L-com1-e1580720605946.png

L-com1-e1580720605946.png

367 ms

L-com-2-e1580720542693.png

L-com-2-e1580720542693.png

381 ms

1470399594_Web_Design-e1580720708900.png

1470399594_Web_Design-e1580720708900.png

436 ms

L-com-8-e1580720766418.png

L-com-8-e1580720766418.png

456 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

32 ms

KFOlCnqEu92Fr1MmWUlfChc9.ttf

KFOlCnqEu92Fr1MmWUlfChc9.ttf

47 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

60 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

76 ms

KFOlCnqEu92Fr1MmEU9fChc9.ttf

KFOlCnqEu92Fr1MmEU9fChc9.ttf

73 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

73 ms

KFOmCnqEu92Fr1Mu7GxP.ttf

KFOmCnqEu92Fr1Mu7GxP.ttf

75 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

74 ms

KFOlCnqEu92Fr1MmSU5fChc9.ttf

KFOlCnqEu92Fr1MmSU5fChc9.ttf

75 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

74 ms

fa-solid-900.woff

fa-solid-900.woff

9206 ms

fa-solid-900.ttf

fa-solid-900.ttf

9208 ms

fa-regular-400.woff

fa-regular-400.woff

350 ms

fa-regular-400.ttf

fa-regular-400.ttf

442 ms

fa-brands-400.ttf

fa-brands-400.ttf

512 ms

fa-solid-900.ttf

fa-solid-900.ttf

9186 ms

fa-regular-400.ttf

fa-regular-400.ttf

444 ms

fa-brands-400.ttf

fa-brands-400.ttf

9187 ms

Accessibility Review

lighty.io accessibility score

88

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.

Best Practices

lighty.io best practices score

92

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

SEO Factors

lighty.io SEO score

93

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lighty.io 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 Lighty.io 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

lighty.io

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