Tools & Wizards About Us
thornlighting.fi screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 0

    Best Practices

  • 84

    SEO

    Google-friendlier than
    52% of websites

thornlighting.fi

Welcome to the Thorn Lighting website — Finland (English)

Page Load Speed

12.1 sec in total

First Response

136 ms

Resources Loaded

11.7 sec

Page Rendered

299 ms

thornlighting.fi screenshot

About Website

Welcome to thornlighting.fi homepage info - get ready to check Thorn Lighting best content right away, or after learning these important things about thornlighting.fi

Thorn Lighting is a globally trusted supplier of both outdoor and indoor luminaires and integrated controls.

Visit thornlighting.fi

Key Findings

We analyzed Thornlighting.fi page load time and found that the first response time was 136 ms and then it took 12 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

thornlighting.fi performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.211

59/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

thornlighting.fi

136 ms

thornlighting.fi

479 ms

www.thornlighting.fi

721 ms

en-fi

589 ms

reset.css

619 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 80% of them (76 requests) were addressed to the original Thornlighting.fi, 4% (4 requests) were made to Thornlighting.com and 3% (3 requests) were made to App.usercentrics.eu. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Thornlighting.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 172.9 kB (10%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thornlighting.fi main page is 1.7 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 44.9 kB

  • Original 56.6 kB
  • After minification 55.6 kB
  • After compression 11.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 44.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 2.3 kB

  • Original 1.0 MB
  • After minification 1.0 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. Thorn Lighting images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 120.3 kB

  • Original 559.0 kB
  • After minification 559.0 kB
  • After compression 438.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 120.3 kB or 22% of the original size.

CSS Optimization

-22%

Potential reduce by 5.4 kB

  • Original 24.7 kB
  • After minification 24.7 kB
  • After compression 19.3 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. Thornlighting.fi needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 61 (73%)

Requests Now

84

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thornlighting.fi

thornlighting.fi

136 ms

thornlighting.fi

thornlighting.fi

479 ms

www.thornlighting.fi

www.thornlighting.fi

721 ms

en-fi

en-fi

589 ms

reset.css

reset.css

619 ms

++resource++collection.css

++resource++collection.css

656 ms

base.css

base.css

673 ms

columns.css

columns.css

654 ms

authoring.css

authoring.css

671 ms

forms.css

forms.css

1264 ms

discussion.css

discussion.css

1248 ms

tinymce.css

tinymce.css

1268 ms

++resource++prettyPhoto.css

++resource++prettyPhoto.css

1265 ms

flowplayer_minimalist.css

flowplayer_minimalist.css

1282 ms

public.css

public.css

1809 ms

default.css

default.css

1859 ms

countries.css

countries.css

1857 ms

casestudies.css

casestudies.css

1860 ms

style.css

style.css

1864 ms

gmap.css

gmap.css

1875 ms

geoip.css

geoip.css

2401 ms

style.css

style.css

2448 ms

ploneCustom.css

ploneCustom.css

2449 ms

gautier-facelift.css

gautier-facelift.css

2451 ms

cookiecuttr.css

cookiecuttr.css

2456 ms

++resource++plone.app.jquery.js

++resource++plone.app.jquery.js

2743 ms

register_function.js

register_function.js

2994 ms

plone_javascript_variables.js

plone_javascript_variables.js

3061 ms

++resource++plone.app.jquerytools.js

++resource++plone.app.jquerytools.js

3042 ms

++resource++plone.app.jquerytools.form.js

++resource++plone.app.jquerytools.form.js

3182 ms

++resource++plone.app.jquerytools.overlayhelpers.js

++resource++plone.app.jquerytools.overlayhelpers.js

3204 ms

++resource++plone.app.jquerytools.plugins.js

++resource++plone.app.jquerytools.plugins.js

3344 ms

++resource++plone.app.jquerytools.tooltip.js

++resource++plone.app.jquerytools.tooltip.js

3587 ms

++resource++plone.app.jquerytools.tooltip.plugins.js

++resource++plone.app.jquerytools.tooltip.plugins.js

3650 ms

nodeutilities.js

nodeutilities.js

3652 ms

cookie_functions.js

cookie_functions.js

3791 ms

modernizr.js

modernizr.js

3814 ms

loader.js

loader.js

17 ms

uc-block.bundle.js

uc-block.bundle.js

22 ms

livesearch.js

livesearch.js

3936 ms

popupforms.js

popupforms.js

3587 ms

dropdown.js

dropdown.js

3593 ms

first_input_focus.js

first_input_focus.js

3598 ms

main.js

main.js

3739 ms

mark_special_links.js

mark_special_links.js

3761 ms

trunk8.js

trunk8.js

3865 ms

flowplayer.js

flowplayer.js

3742 ms

++resource++jquery.prettyPhoto.js

++resource++jquery.prettyPhoto.js

3726 ms

table_sorter.js

table_sorter.js

3600 ms

embed.js

embed.js

4024 ms

application.js

application.js

3773 ms

jquery.autocomplete.min.js

jquery.autocomplete.min.js

3850 ms

formwidget-autocomplete.js

formwidget-autocomplete.js

3648 ms

inline_validation.js

inline_validation.js

3687 ms

++resource++plone.formwidget.querystring.querywidget.js

++resource++plone.formwidget.querystring.querywidget.js

3845 ms

prettyPhoto.js

prettyPhoto.js

3792 ms

search.js

search.js

3870 ms

jquery.cookie.js

jquery.cookie.js

4025 ms

jquery.cookiecuttr.js

jquery.cookiecuttr.js

3651 ms

logo.png

logo.png

1086 ms

adf638c7-0510-412d-b023-17582047321e.png

adf638c7-0510-412d-b023-17582047321e.png

730 ms

e11796d0-a7bd-4a29-aed7-0637374416f4.png

e11796d0-a7bd-4a29-aed7-0637374416f4.png

201 ms

e62a59a4-06e3-4fc9-b75b-b22518b2a125.png

e62a59a4-06e3-4fc9-b75b-b22518b2a125.png

1410 ms

f2b1c081-78c6-4339-a3d9-785fb10c153a.jpeg

f2b1c081-78c6-4339-a3d9-785fb10c153a.jpeg

1085 ms

cfd6a94c-a3cb-4c44-970a-23e6371d6c87.jpeg

cfd6a94c-a3cb-4c44-970a-23e6371d6c87.jpeg

814 ms

92fe0e59-83c0-4334-98d5-81f079f58c1a.jpeg

92fe0e59-83c0-4334-98d5-81f079f58c1a.jpeg

815 ms

b6be5e2c-ee0c-4f2d-b604-4a159ed1965b.jpeg

b6be5e2c-ee0c-4f2d-b604-4a159ed1965b.jpeg

1324 ms

4df0ac75-57af-4110-adb4-706dc440ee61.jpeg

4df0ac75-57af-4110-adb4-706dc440ee61.jpeg

1085 ms

434fe044-ebd6-44f1-83f9-cf53a310205a.jpeg

434fe044-ebd6-44f1-83f9-cf53a310205a.jpeg

1418 ms

afdc4910-3ad4-4a9e-9d84-18e7fa10c7e9.jpeg

afdc4910-3ad4-4a9e-9d84-18e7fa10c7e9.jpeg

1648 ms

7e3318a0-e119-4a39-bf55-5895d9fda47c.png

7e3318a0-e119-4a39-bf55-5895d9fda47c.png

1671 ms

0abbed72-65dd-455b-89e1-4dda9b572d26.png

0abbed72-65dd-455b-89e1-4dda9b572d26.png

2091 ms

gtm.js

gtm.js

198 ms

contenttypes-sprite.png

contenttypes-sprite.png

1907 ms

countries.png

countries.png

2032 ms

bundle_legacy.js

bundle_legacy.js

61 ms

iframe_api

iframe_api

178 ms

FTN45__W.woff

FTN45__W.woff

2358 ms

FTN85__W.woff

FTN85__W.woff

2457 ms

loader.js

loader.js

19 ms

www-widgetapi.js

www-widgetapi.js

4 ms

call-tracking_9.js

call-tracking_9.js

5 ms

languages.json

languages.json

100 ms

wcm

wcm

32 ms

wcm

wcm

13 ms

en.json

en.json

104 ms

1px.png

1px.png

9 ms

translations-en.json

translations-en.json

5 ms

uct

uct

329 ms

logo.png

logo.png

199 ms

4df0ac75-57af-4110-adb4-706dc440ee61.jpeg

4df0ac75-57af-4110-adb4-706dc440ee61.jpeg

28 ms

434fe044-ebd6-44f1-83f9-cf53a310205a.jpeg

434fe044-ebd6-44f1-83f9-cf53a310205a.jpeg

13 ms

afdc4910-3ad4-4a9e-9d84-18e7fa10c7e9.jpeg

afdc4910-3ad4-4a9e-9d84-18e7fa10c7e9.jpeg

15 ms

print.css

print.css

594 ms

mobile.css

mobile.css

591 ms

Accessibility Review

thornlighting.fi accessibility score

81

Accessibility Issues

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.

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.

SEO Factors

thornlighting.fi SEO score

84

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

High

robots.txt is not valid

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thornlighting.fi can be misinterpreted by Google and other search engines. Our service has detected that English 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 Thornlighting.fi 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

thornlighting.fi

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