Tools & Wizards About Us
swam.in screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

swam.in

swam.in Domain Name Is Available to Buy - Domain Name Marketplace

Page Load Speed

1.9 sec in total

First Response

232 ms

Resources Loaded

1.4 sec

Page Rendered

190 ms

swam.in screenshot

About Website

Visit swam.in now to see the best up-to-date Swam content and also check out these interesting facts you probably never knew about swam.in

DaaZ, largest domain marketplace simple, easy & secure platform to buy domain names. Buy this swam.in Domain at best price at DaaZ.

Visit swam.in

Key Findings

We analyzed Swam.in page load time and found that the first response time was 232 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

swam.in performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value1,880 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.285

42/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

swam.in

232 ms

swam.in

230 ms

swam.in

228 ms

googlefonts.css

107 ms

tp.widget.bootstrap.min.js

120 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Swam.in, 85% (29 requests) were made to Daaz.com and 6% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (737 ms) relates to the external source Daaz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 96.9 kB (35%)

Content Size

273.3 kB

After Optimization

176.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Swam.in main page is 273.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. 25% of websites need less resources to load. Images take 173.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 25.7 kB

  • Original 35.7 kB
  • After minification 35.7 kB
  • After compression 10.0 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 25.7 kB or 72% of the original size.

Image Optimization

-40%

Potential reduce by 69.8 kB

  • Original 173.5 kB
  • After minification 103.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, Swam needs image optimization as it can save up to 69.8 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 1.0 kB

  • Original 59.0 kB
  • After minification 59.0 kB
  • After compression 58.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 366 B

  • Original 5.2 kB
  • After minification 5.2 kB
  • After compression 4.8 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. Swam.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (30%)

Requests Now

30

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

swam.in

swam.in

232 ms

swam.in

swam.in

230 ms

swam.in

swam.in

228 ms

googlefonts.css

googlefonts.css

107 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

120 ms

icon.css

icon.css

115 ms

style4.css

style4.css

119 ms

logo.png

logo.png

111 ms

trust-stamp.png

trust-stamp.png

116 ms

paymentgateway-logos.svg

paymentgateway-logos.svg

234 ms

tooltip-icon.png

tooltip-icon.png

212 ms

money-back1.png

money-back1.png

219 ms

transfer1.png

transfer1.png

216 ms

secure-payment1.png

secure-payment1.png

220 ms

twitterX2.png

twitterX2.png

226 ms

money-back-w.png

money-back-w.png

312 ms

money-back-img1.png

money-back-img1.png

326 ms

money-back-img2.png

money-back-img2.png

321 ms

money-back-img3.png

money-back-img3.png

323 ms

jquery.js

jquery.js

334 ms

fittext.js

fittext.js

332 ms

platform.js

platform.js

737 ms

js

js

52 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

v84a3a4012de94ce1a686ba8c167c359c1696973893317

50 ms

transper-img1.png

transper-img1.png

420 ms

transper-img2.png

transper-img2.png

422 ms

secure-payment-img1.png

secure-payment-img1.png

479 ms

secure-payment-img2.png

secure-payment-img2.png

432 ms

fontello.woff

fontello.woff

205 ms

default

default

65 ms

sdk.js

sdk.js

175 ms

view

view

349 ms

js

js

31 ms

main.js

main.js

47 ms

Accessibility Review

swam.in accessibility score

82

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

Best Practices

swam.in best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

swam.in SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Swam.in 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 Swam.in 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

swam.in

Open Graph data is detected on the main page of Swam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: