9.7 sec in total
1.7 sec
7.6 sec
367 ms
Click here to check amazing Dionysos content. Otherwise, check out these important facts you probably never knew about dionysos.se
Grekisk Restaurang på Södermalm, Stockholm. En av de äldsta grekiska restaurangerna i Stockholm sedan 1974. Dionysos tar emot sällskap på upp till 70 personer!
Visit dionysos.seWe analyzed Dionysos.se page load time and found that the first response time was 1.7 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
dionysos.se performance score
name
value
score
weighting
Value10.0 s
0/100
10%
Value21.2 s
0/100
25%
Value17.6 s
0/100
10%
Value800 ms
36/100
30%
Value0.001
100/100
15%
Value21.0 s
1/100
10%
1742 ms
149 ms
264 ms
268 ms
286 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 65% of them (65 requests) were addressed to the original Dionysos.se, 15% (15 requests) were made to Maps.google.com and 9% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Dionysos.se.
Page size can be reduced by 3.0 MB (36%)
8.2 MB
5.3 MB
In fact, the total size of Dionysos.se main page is 8.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. 70% of websites need less resources to load. Images take 5.8 MB which makes up the majority of the site volume.
Potential reduce by 35.6 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 35.6 kB or 81% of the original size.
Potential reduce by 1.1 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. Obviously, Dionysos needs image optimization as it can save up to 1.1 MB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.8 MB
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 1.8 MB or 76% of the original size.
Potential reduce by 53.0 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. Dionysos.se needs all CSS files to be minified and compressed as it can save up to 53.0 kB or 83% of the original size.
Number of requests can be reduced by 53 (56%)
94
41
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dionysos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
dionysos.se
1742 ms
mod_lofarticlesscroller.css
149 ms
nivo-slider.css
264 ms
style.css
268 ms
superfish.css
286 ms
mod_jflanguageselection.css
268 ms
mootools.js
755 ms
caption.js
306 ms
maps
33 ms
mod_yoo_maps.js
387 ms
mod_lofarticlesscroller_jl15x.js
392 ms
jquery.min.js
10 ms
jquery.noconflict.js
390 ms
jquery.nivo.slider.js
574 ms
jquery.js
664 ms
jquery.event.hover.js
513 ms
superfish.js
514 ms
jquery.js
9 ms
cufon-yui.js
642 ms
cufon-replace.js
633 ms
Trajan_Pro_Bold.js
1701 ms
Trajan_Pro_Regular.js
1648 ms
Bickham_Script_Pro_Regular.js
2319 ms
imagepreloader.js
822 ms
template.css
954 ms
ga.js
33 ms
bg_bottom_prev-hover.png
147 ms
bg_bottom_next-hover.png
151 ms
li-a-hover.gif
152 ms
menu-li-first-hover.gif
153 ms
menu-li-hover.gif
176 ms
readon-hover.png
147 ms
news-bg-hover.gif
377 ms
body-bg.jpg
608 ms
extra-bg.jpg
1136 ms
logo.png
425 ms
sv.gif
351 ms
en.gif
398 ms
navigation-bg.png
475 ms
menu-drop-bg.png
501 ms
row-li.png
524 ms
ari-image-slider-wCtrlNav.jpg
787 ms
0.png
2271 ms
01.png
2068 ms
33.png
1863 ms
41.png
1929 ms
42.png
1740 ms
65.png
1425 ms
77.png
1685 ms
81.png
1931 ms
88.png
2249 ms
99.png
2372 ms
history-bg.jpg
2055 ms
dion.png
2075 ms
events-bg.jpg
2183 ms
load-indicator.gif
2190 ms
page1-img3.jpg
2207 ms
thefork_whitewriting.png
2900 ms
reservations.jpg
2362 ms
box-bg.gif
2322 ms
title-bot-bg.png
2354 ms
title-box-bg.gif
2378 ms
__utm.gif
44 ms
location.gif
2324 ms
row.jpg
2711 ms
footer.jpg
2515 ms
common.js
14 ms
map.js
14 ms
overlay.js
11 ms
util.js
11 ms
geocoder.js
10 ms
marker.js
69 ms
loading.gif
171 ms
arrows.png
173 ms
nivo-controlNav-hover.png
171 ms
nivo-controlNav.png
170 ms
onion.js
31 ms
openhand_8_8.cur
22 ms
ViewportInfoService.GetViewportInfo
48 ms
stats.js
16 ms
controls.js
12 ms
transparent.png
18 ms
css
59 ms
infowindow.js
39 ms
google4.png
49 ms
mapcnt6.png
36 ms
sv5.png
37 ms
red-dot.png
21 ms
tmapctrl.png
19 ms
cb_scout5.png
19 ms
tmapctrl4.png
18 ms
imgs8.png
21 ms
vt
9 ms
vt
8 ms
vt
34 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
8 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
16 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
17 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
16 ms
AuthenticationService.Authenticate
263 ms
dionysos.se accessibility score
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
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
dionysos.se 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
dionysos.se SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
SV
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dionysos.se can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and it does not match the claimed English language. Our system also found out that Dionysos.se 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.
dionysos.se
Open Graph description is not detected on the main page of Dionysos. 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: