Tools & Wizards About Us
web.af screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

web.af

WEB.AF

Page Load Speed

1 sec in total

First Response

124 ms

Resources Loaded

758 ms

Page Rendered

122 ms

web.af screenshot

About Website

Visit web.af now to see the best up-to-date WEB content for Afghanistan and also check out these interesting facts you probably never knew about web.af

ویب.اف ارائه دهنده معتبر میزبانی وب در افغانستان با بیش از 500 مشتری فعال.جستجو۹.۸۹$ COM.۱۲.۹۹$ ORG.۲۹.۹۰$ AF.۲۴.۹۹$ COM.AF.۱۴.۹۹$ INFO.۱۲.۹۹$ NET. بسته های میزبانی ویب یک بسته را مطابق نیاز تان انتخا...

Visit web.af

Key Findings

We analyzed Web.af page load time and found that the first response time was 124 ms and then it took 880 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

web.af performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value2,020 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

web.af

124 ms

show_ads.js

5 ms

jsapi

27 ms

logo.gif

41 ms

ca-pub-7537716675008104.js

36 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Web.af, 28% (8 requests) were made to Google.com and 17% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (237 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.6 kB (23%)

Content Size

103.8 kB

After Optimization

80.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Web.af main page is 103.8 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. 45% of websites need less resources to load. Javascripts take 82.0 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 7.6 kB

  • Original 10.7 kB
  • After minification 10.7 kB
  • After compression 3.2 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 7.6 kB or 71% of the original size.

Image Optimization

-13%

Potential reduce by 551 B

  • Original 4.3 kB
  • After minification 3.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. Obviously, WEB needs image optimization as it can save up to 551 B or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 10.0 kB

  • Original 82.0 kB
  • After minification 81.9 kB
  • After compression 72.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 10.0 kB or 12% of the original size.

CSS Optimization

-81%

Potential reduce by 5.5 kB

  • Original 6.7 kB
  • After minification 5.2 kB
  • After compression 1.3 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. Web.af needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (38%)

Requests Now

26

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

web.af

web.af

124 ms

show_ads.js

show_ads.js

5 ms

jsapi

jsapi

27 ms

logo.gif

logo.gif

41 ms

ca-pub-7537716675008104.js

ca-pub-7537716675008104.js

36 ms

zrt_lookup.html

zrt_lookup.html

40 ms

show_ads_impl.js

show_ads_impl.js

123 ms

32 ms

default.css

default.css

23 ms

default+en.css

default+en.css

6 ms

default+en.I.js

default+en.I.js

9 ms

async-ads.js

async-ads.js

126 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

86 ms

small-logo.png

small-logo.png

86 ms

clear.gif

clear.gif

116 ms

ads

ads

237 ms

osd.js

osd.js

24 ms

ads

ads

233 ms

13077156096584944014

13077156096584944014

36 ms

abg.js

abg.js

47 ms

m_js_controller.js

m_js_controller.js

59 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

44 ms

css

css

95 ms

s

s

18 ms

x_button_blue2.png

x_button_blue2.png

20 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

2 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

21 ms

ui

ui

36 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

38 ms

Accessibility Review

web.af accessibility score

74

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Best Practices

web.af best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

web.af SEO score

86

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

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Web.af can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it does not match the claimed English language. Our system also found out that Web.af main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

web.af

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