3.9 sec in total
225 ms
3.5 sec
116 ms
Click here to check amazing Editor content. Otherwise, check out these important facts you probably never knew about editor.si
Izdelava spletnih strani in trgovin, ki prinašajo merljive rezultate. Poslovne spletne rešitve za mobilno poslovanje. Editor že 10 let z vami!
Visit editor.siWe analyzed Editor.si page load time and found that the first response time was 225 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
editor.si performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value5.1 s
25/100
25%
Value5.3 s
58/100
10%
Value170 ms
93/100
30%
Value1
2/100
15%
Value6.5 s
58/100
10%
225 ms
1548 ms
330 ms
540 ms
350 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 78% of them (40 requests) were addressed to the original Editor.si, 8% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Editor.si.
Page size can be reduced by 292.2 kB (34%)
867.3 kB
575.1 kB
In fact, the total size of Editor.si main page is 867.3 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. 45% of websites need less resources to load. Images take 558.9 kB which makes up the majority of the site volume.
Potential reduce by 29.3 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 6.8 kB, which is 18% 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 29.3 kB or 78% of the original size.
Potential reduce by 70.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. Obviously, Editor needs image optimization as it can save up to 70.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 35.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 35.0 kB or 43% of the original size.
Potential reduce by 157.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. Editor.si needs all CSS files to be minified and compressed as it can save up to 157.2 kB or 83% of the original size.
Number of requests can be reduced by 14 (32%)
44
30
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Editor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
editor.si
225 ms
www.editor.si
1548 ms
bootstrap.css
330 ms
style.css
540 ms
css_colors
350 ms
css
39 ms
css
56 ms
respond.js
36 ms
jquery.min.js
23 ms
useful.js
338 ms
bootstrap.min.js
452 ms
email.js
347 ms
ajax.js
442 ms
scripts.js
455 ms
cookie.js
467 ms
prum.min.js
92 ms
gtm.js
116 ms
logo.png
136 ms
92
309 ms
40
287 ms
76
274 ms
895
158 ms
893
173 ms
39
361 ms
82
285 ms
harvey+norman2
306 ms
kolpa2
396 ms
lineasnella2
421 ms
mservis2
431 ms
intelekta2
463 ms
pipistrel2
481 ms
vipava1894v2
536 ms
bazeni24(intex)2
556 ms
soline3
603 ms
37
715 ms
98
650 ms
38
754 ms
2
664 ms
4
684 ms
3
733 ms
google-partner02.png
781 ms
odoo_gold_partner_150px.jpg
796 ms
IBMpartner.png
826 ms
PTP.png
851 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
64 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
70 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
74 ms
YA9Qr0Wd4kDdMtD6GjLCkiE.ttf
44 ms
fontawesome-webfont.woff
905 ms
js
49 ms
editor+test1
235 ms
editor.si accessibility score
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
Form elements do not have associated labels
editor.si 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
editor.si 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
![]()
SL
![]()
SL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Editor.si can be misinterpreted by Google and other search engines. Our service has detected that Slovenian is used on the page, and it matches the claimed language. Our system also found out that Editor.si 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.
editor.si
Open Graph description is not detected on the main page of Editor. 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: