Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

vawda.com

Vawda & Co

Page Load Speed

854 ms in total

First Response

106 ms

Resources Loaded

490 ms

Page Rendered

258 ms

vawda.com screenshot

About Website

Welcome to vawda.com homepage info - get ready to check Vawda best content for Pakistan right away, or after learning these important things about vawda.com

Visit vawda.com

Key Findings

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

Performance Metrics

vawda.com performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/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.024

100/100

15%

TTI (Time to Interactive)

Value4.1 s

87/100

10%

Network Requests Diagram

vawda.com

106 ms

bootstrap.css

85 ms

css

29 ms

style.css

68 ms

animate.css

74 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 76% of them (19 requests) were addressed to the original Vawda.com, 20% (5 requests) were made to Fonts.gstatic.com and 4% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (216 ms) belongs to the original domain Vawda.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 271.3 kB (47%)

Content Size

578.7 kB

After Optimization

307.4 kB

In fact, the total size of Vawda.com main page is 578.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 380.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 20.6 kB

  • Original 24.5 kB
  • After minification 15.5 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 9.0 kB, which is 37% 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 20.6 kB or 84% of the original size.

Image Optimization

-41%

Potential reduce by 155.3 kB

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

JavaScript Optimization

-60%

Potential reduce by 77.7 kB

  • Original 128.8 kB
  • After minification 128.8 kB
  • After compression 51.2 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 77.7 kB or 60% of the original size.

CSS Optimization

-40%

Potential reduce by 17.8 kB

  • Original 45.0 kB
  • After minification 45.0 kB
  • After compression 27.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. Vawda.com needs all CSS files to be minified and compressed as it can save up to 17.8 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (29%)

Requests Now

17

After Optimization

12

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

Accessibility Review

vawda.com accessibility score

79

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

vawda.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

vawda.com SEO score

71

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vawda.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Vawda.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

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