Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

zapleo.com

Zapleo - Digital agency team from Ukraine | ZAPLEOsoft | Home

Page Load Speed

7.5 sec in total

First Response

300 ms

Resources Loaded

5.8 sec

Page Rendered

1.4 sec

zapleo.com screenshot

About Website

Welcome to zapleo.com homepage info - get ready to check Zapleo best content for Ukraine right away, or after learning these important things about zapleo.com

Digital marketing agency, website development agency. We develop website and mobile application ☎ +38 (099) 481-18-89

Visit zapleo.com

Key Findings

We analyzed Zapleo.com page load time and found that the first response time was 300 ms and then it took 7.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

zapleo.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value3,180 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.533

14/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

zapleo.com

300 ms

zapleo.com

1456 ms

js

92 ms

night_1_1600.z.png

859 ms

evening_1_1600.z.png

1147 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 86% of them (25 requests) were addressed to the original Zapleo.com, 7% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Zapleo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 189.7 kB (2%)

Content Size

9.1 MB

After Optimization

9.0 MB

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

HTML Optimization

-73%

Potential reduce by 189.6 kB

  • Original 261.0 kB
  • After minification 241.4 kB
  • After compression 71.4 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 189.6 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.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.

Requests Breakdown

We found no issues to fix!

Requests Now

25

After Optimization

25

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zapleo. According to our analytics all requests are already optimized.

Accessibility Review

zapleo.com accessibility score

63

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

Image elements do not have [alt] attributes

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.

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

zapleo.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

SEO Factors

zapleo.com SEO score

85

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

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

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