Tools & Wizards About Us
swigview.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

swigview.com

SwigView - Multiple YouTube Video Viewer

Page Load Speed

2.3 sec in total

First Response

40 ms

Resources Loaded

2.1 sec

Page Rendered

141 ms

swigview.com screenshot

About Website

Click here to check amazing Swig View content for United States. Otherwise, check out these important facts you probably never knew about swigview.com

SwigView is a Multiple YouTube Video Viewer. View more than one YouTube video, synced, at the same time. A revolutionary way to watch and share videos online.

Visit swigview.com

Key Findings

We analyzed Swigview.com page load time and found that the first response time was 40 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

swigview.com performance score

0

Network Requests Diagram

swigview.com

40 ms

www.swigview.com

51 ms

prototype.js

18 ms

scriptaculous.js

6 ms

functions.js

6 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 82% of them (23 requests) were addressed to the original Swigview.com, 7% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to Reddit.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Swigview.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 199.5 kB (63%)

Content Size

315.5 kB

After Optimization

116.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Swigview.com main page is 315.5 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. 30% of websites need less resources to load. Javascripts take 216.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 23.6 kB

  • Original 30.5 kB
  • After minification 29.2 kB
  • After compression 6.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 23.6 kB or 77% of the original size.

Image Optimization

-20%

Potential reduce by 11.3 kB

  • Original 55.2 kB
  • After minification 43.9 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, Swig View needs image optimization as it can save up to 11.3 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 152.7 kB

  • Original 216.3 kB
  • After minification 173.0 kB
  • After compression 63.6 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 152.7 kB or 71% of the original size.

CSS Optimization

-88%

Potential reduce by 11.9 kB

  • Original 13.5 kB
  • After minification 6.9 kB
  • After compression 1.6 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. Swigview.com needs all CSS files to be minified and compressed as it can save up to 11.9 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (23%)

Requests Now

26

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

swigview.com

swigview.com

40 ms

www.swigview.com

www.swigview.com

51 ms

prototype.js

prototype.js

18 ms

scriptaculous.js

scriptaculous.js

6 ms

functions.js

functions.js

6 ms

swfobject.js

swfobject.js

6 ms

style.css

style.css

828 ms

builder.js

builder.js

14 ms

effects.js

effects.js

12 ms

dragdrop.js

dragdrop.js

15 ms

controls.js

controls.js

15 ms

slider.js

slider.js

1819 ms

sound.js

sound.js

22 ms

ga.js

ga.js

34 ms

playlist.php

playlist.php

29 ms

playlist.php

playlist.php

39 ms

spreddit4.gif

spreddit4.gif

28 ms

SwigViewTop.png

SwigViewTop.png

15 ms

twitter.png

twitter.png

15 ms

widgets.js

widgets.js

42 ms

m94ndn9.jpg

m94ndn9.jpg

32 ms

msahaAw.jpg

msahaAw.jpg

30 ms

default.png

default.png

31 ms

k6yRy9E.jpg

k6yRy9E.jpg

30 ms

sN4MBYj.jpg

sN4MBYj.jpg

26 ms

vrJaTIM.jpg

vrJaTIM.jpg

25 ms

__utm.gif

__utm.gif

15 ms

nr-892.min.js

nr-892.min.js

40 ms

SEO Factors

swigview.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Swigview.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Swigview.com 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

swigview.com

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