Tools & Wizards About Us
afes.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

afes.com

Page Load Speed

1.7 sec in total

First Response

217 ms

Resources Loaded

1.3 sec

Page Rendered

205 ms

afes.com screenshot

About Website

Welcome to afes.com homepage info - get ready to check Afes best content right away, or after learning these important things about afes.com

Visit afes.com

Key Findings

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

Performance Metrics

afes.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

afes.com

217 ms

toc.htm

234 ms

index2.htm

306 ms

grngrnbk.gif

69 ms

dollar2.gif

139 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Afes.com, 67% (24 requests) were made to Yolo.net and 8% (3 requests) were made to W.24timezones.com. The less responsive or slowest element that took the longest time to load (409 ms) relates to the external source Cdn.perfops.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.1 kB (32%)

Content Size

144.4 kB

After Optimization

98.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Afes.com main page is 144.4 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. 15% of websites need less resources to load. Images take 138.0 kB which makes up the majority of the site volume.

HTML Optimization

-43%

Potential reduce by 154 B

  • Original 360 B
  • After minification 352 B
  • After compression 206 B

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 154 B or 43% of the original size.

Image Optimization

-33%

Potential reduce by 46.0 kB

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

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 2.8 kB
  • After minification 2.8 kB
  • After compression 2.8 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

-0%

Potential reduce by 0 B

  • Original 3.2 kB
  • After minification 3.2 kB
  • After compression 3.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. Afes.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

34

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

afes.com

afes.com

217 ms

toc.htm

toc.htm

234 ms

index2.htm

index2.htm

306 ms

grngrnbk.gif

grngrnbk.gif

69 ms

dollar2.gif

dollar2.gif

139 ms

aup.gif

aup.gif

139 ms

mailslot.gif

mailslot.gif

146 ms

vme.gif

vme.gif

145 ms

wvm.gif

wvm.gif

145 ms

dvm.gif

dvm.gif

145 ms

gvm.gif

gvm.gif

221 ms

fvm_s.gif

fvm_s.gif

213 ms

rvm.gif

rvm.gif

223 ms

grngrnb2.gif

grngrnb2.gif

221 ms

logo.gif

logo.gif

283 ms

usflag.gif

usflag.gif

361 ms

siteseal.js

siteseal.js

133 ms

l.js

l.js

81 ms

sep24_2023_sw.png

sep24_2023_sw.png

366 ms

paypalvisamcsm.jpg

paypalvisamcsm.jpg

270 ms

google.gif

google.gif

203 ms

lycos.gif

lycos.gif

213 ms

yahoo.gif

yahoo.gif

212 ms

sblbutton.gif

sblbutton.gif

271 ms

apache.gif

apache.gif

282 ms

freebsd.gif

freebsd.gif

283 ms

sbsdlogo.gif

sbsdlogo.gif

290 ms

sorbsbtn.gif

sorbsbtn.gif

339 ms

search.html

search.html

34 ms

Seal.aspx

Seal.aspx

47 ms

rom3.min.js

rom3.min.js

47 ms

c.js

c.js

118 ms

logo_icon60.v101.png

logo_icon60.v101.png

11 ms

search_dropdown_homepage.v102.png

search_dropdown_homepage.v102.png

12 ms

clock_widget.css

clock_widget.css

13 ms

es6-promise.min.js

es6-promise.min.js

409 ms

Best Practices

afes.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

SEO Factors

afes.com SEO score

55

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Afes.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Afes.com 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

afes.com

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