Tools & Wizards About Us
fess.ir screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

fess.ir

Dr. Mohsen Naraghi Official Website

Page Load Speed

10.5 sec in total

First Response

703 ms

Resources Loaded

9.6 sec

Page Rendered

111 ms

fess.ir screenshot

About Website

Visit fess.ir now to see the best up-to-date Fess content and also check out these interesting facts you probably never knew about fess.ir

Dr. Mohsen Naraghi, Rhinologist, Facial Plastic Surgeon Official Website

Visit fess.ir

Key Findings

We analyzed Fess.ir page load time and found that the first response time was 703 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

fess.ir performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

79/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

94/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

fess.ir

703 ms

7305 ms

p30weblinks.css

188 ms

mootools.js

534 ms

caption.js

353 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fess.ir, 98% (41 requests) were made to Drnaraghi.ir. The less responsive or slowest element that took the longest time to load (7.3 sec) relates to the external source Drnaraghi.ir.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.1 kB (10%)

Content Size

279.1 kB

After Optimization

250.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fess.ir main page is 279.1 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 196.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 14.1 kB

  • Original 18.0 kB
  • After minification 16.1 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 1.9 kB, which is 11% 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 14.1 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 10.6 kB

  • Original 196.2 kB
  • After minification 185.6 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. Fess images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.3 kB

  • Original 56.2 kB
  • After minification 56.2 kB
  • After compression 54.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.

CSS Optimization

-24%

Potential reduce by 2.1 kB

  • Original 8.6 kB
  • After minification 8.6 kB
  • After compression 6.5 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. Fess.ir needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (51%)

Requests Now

39

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fess.ir

fess.ir

703 ms

7305 ms

p30weblinks.css

p30weblinks.css

188 ms

mootools.js

mootools.js

534 ms

caption.js

caption.js

353 ms

system.css

system.css

355 ms

general.css

general.css

361 ms

template.css

template.css

364 ms

jquery.js

jquery.js

541 ms

script.js

script.js

527 ms

p30weblinks.js

p30weblinks.js

530 ms

Bottom_texture.jpg

Bottom_texture.jpg

176 ms

sheet_b.png

sheet_b.png

181 ms

sheet_t.png

sheet_t.png

177 ms

sheet.png

sheet.png

175 ms

header.png

header.png

722 ms

nav.png

nav.png

175 ms

menuitem.png

menuitem.png

350 ms

spacer.gif

spacer.gif

350 ms

subitem.png

subitem.png

351 ms

block_b.png

block_b.png

352 ms

block_t.png

block_t.png

358 ms

block.png

block.png

527 ms

blockheader.png

blockheader.png

528 ms

webset2.png

webset2.png

527 ms

ir_flag.gif

ir_flag.gif

530 ms

uk_flag.gif

uk_flag.gif

539 ms

uae_flag.gif

uae_flag.gif

715 ms

cn_flag.gif

cn_flag.gif

721 ms

de_flag.jpg

de_flag.jpg

715 ms

fr_flag.jpg

fr_flag.jpg

714 ms

es_flag.jpg

es_flag.jpg

738 ms

it_flag.jpg

it_flag.jpg

891 ms

link.gif

link.gif

883 ms

desc.gif

desc.gif

883 ms

blockcontentbullets.png

blockcontentbullets.png

900 ms

post_b.png

post_b.png

884 ms

post_t.png

post_t.png

913 ms

post.png

post.png

1060 ms

webset1.png

webset1.png

1065 ms

0footer_b.png

0footer_b.png

1067 ms

footer.jpg

footer.jpg

1068 ms

Accessibility Review

fess.ir accessibility score

75

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

<object> elements do not have alternate text

Best Practices

fess.ir best practices score

50

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

SEO Factors

fess.ir SEO score

62

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

High

Document uses plugins

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 Fess.ir 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 Fess.ir 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

fess.ir

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