Tools & Wizards About Us
lecta.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

lecta.com

Lecta | Premier supplier of paper-based solutions worldwide

Page Load Speed

4.3 sec in total

First Response

311 ms

Resources Loaded

3.8 sec

Page Rendered

197 ms

lecta.com screenshot

About Website

Click here to check amazing Lecta content for Spain. Otherwise, check out these important facts you probably never knew about lecta.com

Lecta, premier supplier of papers for labels, flexible packaging, commercial printing, publishing, thermal printing, business forms and self-adhesives

Visit lecta.com

Key Findings

We analyzed Lecta.com page load time and found that the first response time was 311 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

lecta.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.3 s

0/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.414

23/100

15%

TTI (Time to Interactive)

Value25.1 s

0/100

10%

Network Requests Diagram

lecta.com

311 ms

lecta.com

510 ms

en

861 ms

gtm.js

168 ms

slick.css

204 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 81% of them (85 requests) were addressed to the original Lecta.com, 9% (9 requests) were made to Cdn.cookielaw.org and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Lecta.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.7 kB (7%)

Content Size

3.1 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lecta.com main page is 3.1 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. 55% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 169.2 kB

  • Original 220.3 kB
  • After minification 213.8 kB
  • After compression 51.1 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 169.2 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 555 B

  • Original 1.8 MB
  • After minification 1.8 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. Lecta images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 6.2 kB

  • Original 905.0 kB
  • After minification 905.0 kB
  • After compression 898.8 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

-24%

Potential reduce by 41.8 kB

  • Original 175.9 kB
  • After minification 165.3 kB
  • After compression 134.1 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. Lecta.com needs all CSS files to be minified and compressed as it can save up to 41.8 kB or 24% of the original size.

Requests Breakdown

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

Requests Now

100

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lecta.com

lecta.com

311 ms

lecta.com

lecta.com

510 ms

en

en

861 ms

gtm.js

gtm.js

168 ms

slick.css

slick.css

204 ms

slick-theme.css

slick-theme.css

301 ms

corev15.css

corev15.css

496 ms

bootstrap.min.css

bootstrap.min.css

401 ms

font-awesome.min.css

font-awesome.min.css

305 ms

owl.carousel.min.css

owl.carousel.min.css

306 ms

owl.theme.default.min.css

owl.theme.default.min.css

309 ms

bootstrap-select.min.css

bootstrap-select.min.css

405 ms

bootstrap-submenu.min.css

bootstrap-submenu.min.css

408 ms

main.css

main.css

610 ms

styles-restyling.css

styles-restyling.css

417 ms

searchv15.css

searchv15.css

506 ms

editmode15.css

editmode15.css

511 ms

initstrings.js

initstrings.js

512 ms

init.js

init.js

630 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

598 ms

bootstrap.min.js

bootstrap.min.js

607 ms

bootstrap-submenu.min.js

bootstrap-submenu.min.js

608 ms

bootstrap-select.min.js

bootstrap-select.min.js

627 ms

genericfunctions.js

genericfunctions.js

696 ms

Init.js

Init.js

713 ms

theming.js

theming.js

804 ms

ScriptResource.axd

ScriptResource.axd

721 ms

blank.js

blank.js

715 ms

ScriptResource.axd

ScriptResource.axd

735 ms

sp.res.js

sp.res.js

798 ms

sp.runtime.js

sp.runtime.js

820 ms

sp.init.js

sp.init.js

820 ms

sp.search.js

sp.search.js

826 ms

clientrenderer.js

clientrenderer.js

837 ms

srch.resources.js

srch.resources.js

902 ms

search.clientcontrols.js

search.clientcontrols.js

1004 ms

search.cbs.js

search.cbs.js

921 ms

css

css

29 ms

css2

css2

48 ms

WebResource.axd

WebResource.axd

832 ms

ScriptResource.axd

ScriptResource.axd

836 ms

api.js

api.js

33 ms

Home.js

Home.js

858 ms

slick.min.js

slick.min.js

838 ms

corporate.jpg

corporate.jpg

766 ms

spcommon.png

spcommon.png

165 ms

FaviconLecta32x32.gif

FaviconLecta32x32.gif

115 ms

logoLecta.svg

logoLecta.svg

163 ms

lupa.svg

lupa.svg

114 ms

b_SustainabilityHome.jpg

b_SustainabilityHome.jpg

436 ms

b_SustainabilityHome_mobile.jpg

b_SustainabilityHome_mobile.jpg

440 ms

rrss.jpg

rrss.jpg

435 ms

rrss_mobile.jpg

rrss_mobile.jpg

515 ms

lkn.png

lkn.png

227 ms

nl.png

nl.png

227 ms

youtube.png

youtube.png

333 ms

lkn_bk.png

lkn_bk.png

334 ms

tw_bk.png

tw_bk.png

438 ms

nl_bk.png

nl_bk.png

440 ms

sustainability.jpg

sustainability.jpg

664 ms

slick.css

slick.css

465 ms

slick-theme.css

slick-theme.css

493 ms

corev15.css

corev15.css

638 ms

bootstrap.min.css

bootstrap.min.css

535 ms

font-awesome.min.css

font-awesome.min.css

531 ms

owl.carousel.min.css

owl.carousel.min.css

567 ms

owl.theme.default.min.css

owl.theme.default.min.css

596 ms

bootstrap-select.min.css

bootstrap-select.min.css

601 ms

bootstrap-submenu.min.css

bootstrap-submenu.min.css

634 ms

main.css

main.css

658 ms

styles-restyling.css

styles-restyling.css

670 ms

searchv15.css

searchv15.css

695 ms

editmode15.css

editmode15.css

702 ms

insight.min.js

insight.min.js

81 ms

otSDKStub.js

otSDKStub.js

73 ms

select-arrow.png

select-arrow.png

733 ms

flecha_bl.svg

flecha_bl.svg

871 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiukDT.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiukDT.woff

65 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvUDT.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvUDT.woff

74 ms

recaptcha__en.js

recaptcha__en.js

69 ms

SP.Web.GetContextWebThemeData

SP.Web.GetContextWebThemeData

821 ms

searchcenterurl

searchcenterurl

742 ms

strings.js

strings.js

752 ms

ProcessQuery

ProcessQuery

1018 ms

ProcessQuery

ProcessQuery

1032 ms

item_lectahomecategory.js

item_lectahomecategory.js

745 ms

group_content.js

group_content.js

773 ms

4b9f5708-2b6e-4631-b023-9308f1cdc164-test.json

4b9f5708-2b6e-4631-b023-9308f1cdc164-test.json

96 ms

insight_tag_errors.gif

insight_tag_errors.gif

143 ms

control_lectahomecategory.js

control_lectahomecategory.js

834 ms

item_lectanoticiashomerestyling.js

item_lectanoticiashomerestyling.js

865 ms

control_lectanoticiashomerestyling.js

control_lectanoticiashomerestyling.js

838 ms

otBannerSdk.js

otBannerSdk.js

18 ms

en.json

en.json

97 ms

otCenterRounded.json

otCenterRounded.json

19 ms

otPcCenter.json

otPcCenter.json

26 ms

otCookieSettingsButton.json

otCookieSettingsButton.json

20 ms

LogoLecta.png

LogoLecta.png

34 ms

powered_by_logo.svg

powered_by_logo.svg

15 ms

core.js

core.js

203 ms

customstrings.js

customstrings.js

107 ms

mquery.js

mquery.js

104 ms

sp.core.js

sp.core.js

108 ms

corev15.css

corev15.css

118 ms

CustomStrings.js

CustomStrings.js

106 ms

Accessibility Review

lecta.com accessibility score

88

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

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

lecta.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

lecta.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Lecta.com 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 Lecta.com 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

lecta.com

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