4.8 sec in total
489 ms
3.9 sec
375 ms
Click here to check amazing Dev Zalle content for Romania. Otherwise, check out these important facts you probably never knew about dev.zalle.work
Web design Bucharest - Web Development Bucharest - web design agency Bucharest - custom web development – Zalle Development srl
Visit dev.zalle.workWe analyzed Dev.zalle.work page load time and found that the first response time was 489 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
dev.zalle.work performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value6.3 s
10/100
25%
Value9.7 s
11/100
10%
Value250 ms
84/100
30%
Value0.473
18/100
15%
Value10.6 s
23/100
10%
489 ms
548 ms
528 ms
77 ms
93 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 Dev.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.5 sec) relates to the external source Zalle.ro.
Page size can be reduced by 102.4 kB (5%)
2.2 MB
2.1 MB
In fact, the total size of Dev.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.
Potential reduce by 41.9 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.
Potential reduce by 27.7 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. Dev Zalle images are well optimized though.
Potential reduce by 32.0 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 32.0 kB or 21% of the original size.
Potential reduce by 719 B
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. Dev.zalle.work has all CSS files already compressed.
Number of requests can be reduced by 27 (43%)
63
36
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dev 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.
dev.zalle.work
489 ms
www.zalle.ro
548 ms
www.zalle.ro
528 ms
css
77 ms
css
93 ms
font-awesome.min.css
67 ms
jquery-ui.css
59 ms
normalize.css
125 ms
main.css
250 ms
bootstrap.css
496 ms
styles-bootstrap.css
489 ms
style.css
502 ms
mediascreen.css
374 ms
cookieconsent.min.css
67 ms
cookieconsent.min.js
75 ms
202897.js
80 ms
jquery.min.js
66 ms
jquery-ui.min.js
72 ms
modernizr-2.6.2.min.js
371 ms
bootstrap.min.js
370 ms
bootstrap-select.min.js
81 ms
jquery.devrama.slider.js
551 ms
moment.min.js
95 ms
map_effect.js
550 ms
jquery.bxslider.min.js
551 ms
jquery-migrate-1.2.1.min.js
61 ms
jquery.reveal.js
655 ms
main.js
654 ms
newsletter.js
654 ms
hotjar-568400.js
145 ms
zallerosu.svg
142 ms
m_zalleroz.svg
144 ms
online-shops_01.jpg
668 ms
responsive_01.png
611 ms
Z_Cinemagraph_02.gif
968 ms
smile1.png
376 ms
smile2.png
413 ms
smile3.png
420 ms
smile4.png
494 ms
smile5.png
540 ms
planning_strategy.png
546 ms
design_visual.png
618 ms
development.png
660 ms
performance.png
676 ms
social_media.png
736 ms
analytics.js
137 ms
language.svg
713 ms
scroll-down-default-redArrow.svg
754 ms
tablet.png
888 ms
scroll-down-default-whiteArrow.svg
768 ms
GoTo-arrow-white.svg
833 ms
process.svg
836 ms
sprites.png
877 ms
GoTo-arrow-grey.svg
893 ms
close_popup.png
958 ms
check.png
961 ms
footer2.jpg
1479 ms
map_footer.png
1013 ms
hotspot.png
1018 ms
go_top.png
1060 ms
go_bottom.png
1081 ms
divider_menu.png
980 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf
204 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdr.ttf
205 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf
232 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9U6Vc.ttf
240 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAjBO9U6Vc.ttf
254 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9U6Vc.ttf
253 ms
fontawesome-webfont.woff
202 ms
collect
125 ms
js
55 ms
slide_portofolio1.jpg
889 ms
slide_portofolio2.jpg
499 ms
dev.zalle.work accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
<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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dev.zalle.work best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
dev.zalle.work SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
EN
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dev.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 Dev.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.
dev.zalle.work
Open Graph description is not detected on the main page of Dev 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: