Tools & Wizards About Us
api.zwayam.com screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

api.zwayam.com

Zwayam | Create your career site powered talent sourcing platform

Page Load Speed

3.4 sec in total

First Response

268 ms

Resources Loaded

3.1 sec

Page Rendered

49 ms

api.zwayam.com screenshot

About Website

Visit api.zwayam.com now to see the best up-to-date Api Zwayam content for India and also check out these interesting facts you probably never knew about api.zwayam.com

Create your career site powered talent sourcing platform. Your journey to a great career site starts here. Get your Digital, Social & Mobile enabled career site created. It is easy to customize and FR...

Visit api.zwayam.com

Key Findings

We analyzed Api.zwayam.com page load time and found that the first response time was 268 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

api.zwayam.com performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

api.zwayam.com

268 ms

googlefonts.css

1004 ms

bootstrap.min.css

1156 ms

font-awesome.min.css

1131 ms

animate.min.css

1184 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 88% of them (14 requests) were addressed to the original Api.zwayam.com, 13% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Api.zwayam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.9 kB (20%)

Content Size

30.4 kB

After Optimization

24.5 kB

  • HTML
  • JavaScript

In fact, the total size of Api.zwayam.com main page is 30.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 21.0 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 5.9 kB

  • Original 9.4 kB
  • After minification 8.1 kB
  • After compression 3.5 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 1.3 kB, which is 14% 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 5.9 kB or 63% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

  • AJAX
  • JavaScript

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Api Zwayam. According to our analytics all requests are already optimized.

Network Requests Diagram

api.zwayam.com

api.zwayam.com

268 ms

googlefonts.css

googlefonts.css

1004 ms

bootstrap.min.css

bootstrap.min.css

1156 ms

font-awesome.min.css

font-awesome.min.css

1131 ms

animate.min.css

animate.min.css

1184 ms

ngActivityIndicator.min.css

ngActivityIndicator.min.css

1032 ms

ngDialog.css

ngDialog.css

1163 ms

ngDialog-theme-default.css

ngDialog-theme-default.css

2005 ms

style.css

style.css

1307 ms

customstyle.css

customstyle.css

2353 ms

jquery-responsiveGallery.css

jquery-responsiveGallery.css

2251 ms

toaster.min.css

toaster.min.css

2332 ms

orange.css

orange.css

2276 ms

analytics.js

analytics.js

19 ms

logo.png

logo.png

256 ms

collect

collect

13 ms

Accessibility Review

api.zwayam.com accessibility score

52

Accessibility Issues

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

api.zwayam.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

api.zwayam.com SEO score

92

Search Engine Optimization Advices

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

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 Api.zwayam.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 Api.zwayam.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

api.zwayam.com

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