Tools & Wizards About Us
zalle.work screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

zalle.work

Web design Bucharest, web development Bucharest, web design agency, custom website development - Zalle Development

Page Load Speed

4.9 sec in total

First Response

381 ms

Resources Loaded

4.1 sec

Page Rendered

419 ms

zalle.work screenshot

About Website

Welcome to zalle.work homepage info - get ready to check Zalle best content for Romania right away, or after learning these important things about zalle.work

Web design Bucharest - Web Development Bucharest - web design agency Bucharest - custom web development – Zalle Development srl

Visit zalle.work

Key Findings

We analyzed Zalle.work page load time and found that the first response time was 381 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

zalle.work performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.465

19/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

zalle.work

381 ms

www.zalle.ro

591 ms

www.zalle.ro

534 ms

css

48 ms

css

65 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Zalle.work, 67% (49 requests) were made to Zalle.ro and 8% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Zalle.ro.

Page Optimization Overview & Recommendations

Page size can be reduced by 70.5 kB (3%)

Content Size

2.2 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zalle.work main page is 2.2 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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 41.9 kB

  • Original 51.1 kB
  • After minification 38.5 kB
  • After compression 9.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 12.7 kB, which is 25% 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 41.9 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 27.7 kB

  • Original 2.0 MB
  • After minification 2.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. Zalle images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 86 B

  • Original 119.0 kB
  • After minification 119.0 kB
  • After compression 118.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

-9%

Potential reduce by 719 B

  • Original 8.1 kB
  • After minification 8.1 kB
  • After compression 7.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. Zalle.work has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (43%)

Requests Now

63

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zalle.work

zalle.work

381 ms

www.zalle.ro

www.zalle.ro

591 ms

www.zalle.ro

www.zalle.ro

534 ms

css

css

48 ms

css

css

65 ms

font-awesome.min.css

font-awesome.min.css

41 ms

jquery-ui.css

jquery-ui.css

35 ms

normalize.css

normalize.css

127 ms

main.css

main.css

252 ms

bootstrap.css

bootstrap.css

488 ms

styles-bootstrap.css

styles-bootstrap.css

482 ms

style.css

style.css

493 ms

mediascreen.css

mediascreen.css

365 ms

cookieconsent.min.css

cookieconsent.min.css

49 ms

cookieconsent.min.js

cookieconsent.min.js

64 ms

202897.js

202897.js

65 ms

jquery.min.js

jquery.min.js

36 ms

jquery-ui.min.js

jquery-ui.min.js

40 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

365 ms

bootstrap.min.js

bootstrap.min.js

374 ms

bootstrap-select.min.js

bootstrap-select.min.js

61 ms

jquery.devrama.slider.js

jquery.devrama.slider.js

525 ms

moment.min.js

moment.min.js

65 ms

map_effect.js

map_effect.js

525 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

525 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

33 ms

jquery.reveal.js

jquery.reveal.js

606 ms

main.js

main.js

607 ms

newsletter.js

newsletter.js

607 ms

hotjar-568400.js

hotjar-568400.js

108 ms

zallerosu.svg

zallerosu.svg

242 ms

m_zalleroz.svg

m_zalleroz.svg

240 ms

online-shops_01.jpg

online-shops_01.jpg

631 ms

responsive_01.png

responsive_01.png

600 ms

Z_Cinemagraph_02.gif

Z_Cinemagraph_02.gif

738 ms

smile1.png

smile1.png

385 ms

smile2.png

smile2.png

406 ms

smile3.png

smile3.png

400 ms

smile4.png

smile4.png

507 ms

smile5.png

smile5.png

523 ms

planning_strategy.png

planning_strategy.png

531 ms

design_visual.png

design_visual.png

628 ms

development.png

development.png

645 ms

performance.png

performance.png

654 ms

social_media.png

social_media.png

719 ms

analytics.js

analytics.js

103 ms

language.svg

language.svg

731 ms

scroll-down-default-redArrow.svg

scroll-down-default-redArrow.svg

735 ms

tablet.png

tablet.png

867 ms

scroll-down-default-whiteArrow.svg

scroll-down-default-whiteArrow.svg

760 ms

GoTo-arrow-white.svg

GoTo-arrow-white.svg

821 ms

process.svg

process.svg

839 ms

sprites.png

sprites.png

850 ms

GoTo-arrow-grey.svg

GoTo-arrow-grey.svg

858 ms

close_popup.png

close_popup.png

884 ms

check.png

check.png

941 ms

footer2.jpg

footer2.jpg

1078 ms

map_footer.png

map_footer.png

971 ms

hotspot.png

hotspot.png

981 ms

go_top.png

go_top.png

988 ms

go_bottom.png

go_bottom.png

1008 ms

divider_menu.png

divider_menu.png

982 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf

140 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdr.ttf

164 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf

171 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9U6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9U6Vc.ttf

187 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAjBO9U6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAjBO9U6Vc.ttf

186 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9U6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9U6Vc.ttf

187 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

53 ms

collect

collect

113 ms

js

js

61 ms

slide_portofolio1.jpg

slide_portofolio1.jpg

1157 ms

slide_portofolio2.jpg

slide_portofolio2.jpg

619 ms

Accessibility Review

zalle.work accessibility score

86

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

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

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

zalle.work 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

Page has valid source maps

SEO Factors

zalle.work SEO score

91

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

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 Zalle.work 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 Zalle.work 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

zalle.work

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