4.8 sec in total
280 ms
4.3 sec
221 ms
Visit sway.se now to see the best up-to-date Sway content and also check out these interesting facts you probably never knew about sway.se
Letar du efter en bra dansskola? Eller är du intresserad av träning och yoga? Sway ger dig ett brett utbud av dans och träning! Danskurser inom bland annat street, jazz och show. Vi erbjuder även kurs...
Visit sway.seWe analyzed Sway.se page load time and found that the first response time was 280 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
sway.se performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value7.1 s
5/100
25%
Value5.0 s
63/100
10%
Value90 ms
99/100
30%
Value0.115
86/100
15%
Value6.0 s
65/100
10%
280 ms
441 ms
12 ms
312 ms
325 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 23% of them (11 requests) were addressed to the original Sway.se, 45% (21 requests) were made to Static.xx.fbcdn.net and 15% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Sway.se.
Page size can be reduced by 109.4 kB (21%)
521.7 kB
412.4 kB
In fact, the total size of Sway.se main page is 521.7 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. 35% of websites need less resources to load. Images take 419.1 kB which makes up the majority of the site volume.
Potential reduce by 12.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. 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 12.9 kB or 71% of the original size.
Potential reduce by 41.8 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. Sway images are well optimized though.
Potential reduce by 8.5 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 8.5 kB or 30% of the original size.
Potential reduce by 46.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. Sway.se needs all CSS files to be minified and compressed as it can save up to 46.2 kB or 82% of the original size.
Number of requests can be reduced by 20 (43%)
46
26
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sway. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
280 ms
style.css
441 ms
jquery.min.js
12 ms
plugins.js
312 ms
script.js
325 ms
logo_pink.png
339 ms
shutterstock_177635609_liten3.jpg
1056 ms
c7826c3c2bc90fb46309141cfefbce0c1cce2c91.jpg
368 ms
7af609e68a79fbe1881f5663d0c6458dc4cbb08f.jpg
482 ms
fb_white_icon.png
526 ms
swoosh.png
305 ms
ga.js
7 ms
sdk.js
271 ms
1789 ms
__utm.gif
10 ms
203 ms
xd_arbiter.php
214 ms
xd_arbiter.php
420 ms
like_box.php
201 ms
kyEKgjk51ZE.css
283 ms
xgj7bXhJNEH.css
346 ms
Czh0gDTFcBt.css
414 ms
N-k91nHCZS2.css
547 ms
ZeuPykSxSED.css
554 ms
q68gy-v_YMF.js
584 ms
FJmpeSpHpjS.js
616 ms
0wM5s1Khldu.js
481 ms
1bNoFZUdlYZ.js
479 ms
njO1TPvGzoR.js
566 ms
1QuX41zDRrx.js
564 ms
Oagsvfb4VWi.js
678 ms
LTv6ZK-5zxz.js
812 ms
1FCa-btixu2.js
682 ms
10367716_735218776542669_6556209550632918329_n.jpg
346 ms
389672_373877099343507_1593264457_n.jpg
475 ms
1463396_1006695559390011_4770346475881751510_n.jpg
653 ms
549755_10151412053518912_714047623_n.jpg
539 ms
10430468_10152458310602687_6396461995014386910_n.jpg
584 ms
12373398_10153092461697581_5205479406489890473_n.jpg
540 ms
67677_1113861808678362_7675706380622844100_n.jpg
722 ms
wL6VQj7Ab77.png
84 ms
s7jcwEQH7Sx.png
85 ms
QDwYpIaRyfG.png
85 ms
pimRBh7B6ER.png
85 ms
aeO1ik7i7-T.png
270 ms
I6-MnjEovm5.js
68 ms
pQrUxxo5oQp.js
136 ms
sway.se 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
sway.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
sway.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 Sway.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 Sway.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.
sway.se
Open Graph description is not detected on the main page of Sway. 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: