Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

zap.lu

Zap

Page Load Speed

16.9 sec in total

First Response

1.1 sec

Resources Loaded

6 sec

Page Rendered

9.9 sec

zap.lu screenshot

About Website

Welcome to zap.lu homepage info - get ready to check Zap best content right away, or after learning these important things about zap.lu

Zap S.A. creates Enterprise Social Collaboration Solutions

Visit zap.lu

Key Findings

We analyzed Zap.lu page load time and found that the first response time was 1.1 sec and then it took 15.9 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

zap.lu performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.0 s

33/100

10%

Network Requests Diagram

zap.lu

1054 ms

zap.lu

560 ms

www.zap.lu

530 ms

www.zap.lu

445 ms

css

770 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 75% of them (12 requests) were addressed to the original Zap.lu, 13% (2 requests) were made to Cdnjs.cloudflare.com and 6% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Zap.lu.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.5 kB (33%)

Content Size

450.7 kB

After Optimization

302.2 kB

In fact, the total size of Zap.lu main page is 450.7 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. 25% of websites need less resources to load. Images take 276.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 6.8 kB

  • Original 9.0 kB
  • After minification 6.4 kB
  • After compression 2.2 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 2.6 kB, which is 29% 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 6.8 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 9.1 kB

  • Original 276.4 kB
  • After minification 267.3 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. Zap images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 29.0 kB

  • Original 40.5 kB
  • After minification 40.5 kB
  • After compression 11.5 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 29.0 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 103.5 kB

  • Original 124.7 kB
  • After minification 123.8 kB
  • After compression 21.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. Zap.lu needs all CSS files to be minified and compressed as it can save up to 103.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (25%)

Requests Now

12

After Optimization

9

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

Accessibility Review

zap.lu accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

[role]s are not contained by their required parent element

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

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

zap.lu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

zap.lu SEO score

54

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

robots.txt is not valid

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zap.lu can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Zap.lu 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

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