Tools & Wizards About Us
nadersaab.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

nadersaab.com

Plastic Surgery Lebanon | Cosmetic treatment - Dr. Nader Saab

Page Load Speed

1.2 sec in total

First Response

45 ms

Resources Loaded

553 ms

Page Rendered

631 ms

nadersaab.com screenshot

About Website

Visit nadersaab.com now to see the best up-to-date Nader Saab content and also check out these interesting facts you probably never knew about nadersaab.com

An aesthetic and cosmetic Surgeon providing cosmetic, aesthetic and plastic surgery for Lebanon and the Middle East. Explore site to know more!

Visit nadersaab.com

Key Findings

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

Performance Metrics

nadersaab.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value420 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.3

39/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

nadersaab.com

45 ms

www.nadersaab.com

121 ms

analytics.js

20 ms

jquery-1.7.2.min.js

7 ms

css

37 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 72% of them (57 requests) were addressed to the original Nadersaab.com, 10% (8 requests) were made to I.ytimg.com and 8% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (201 ms) belongs to the original domain Nadersaab.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 205.5 kB (16%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nadersaab.com main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 861.7 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 157.8 kB

  • Original 218.2 kB
  • After minification 218.1 kB
  • After compression 60.4 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 157.8 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 11.0 kB

  • Original 861.7 kB
  • After minification 850.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. Nader Saab images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 36.5 kB

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

CSS Optimization

-22%

Potential reduce by 272 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 959 B

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. Nadersaab.com needs all CSS files to be minified and compressed as it can save up to 272 B or 22% of the original size.

Requests Breakdown

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

Requests Now

71

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nadersaab.com

nadersaab.com

45 ms

www.nadersaab.com

www.nadersaab.com

121 ms

analytics.js

analytics.js

20 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

7 ms

css

css

37 ms

jscss.php

jscss.php

63 ms

jquery.min.js

jquery.min.js

84 ms

jquery-noconflict.js

jquery-noconflict.js

44 ms

jquery-migrate.min.js

jquery-migrate.min.js

54 ms

tabs-state.js

tabs-state.js

52 ms

caption.js

caption.js

52 ms

mootools-core.js

mootools-core.js

93 ms

core.js

core.js

77 ms

mootools-more.js

mootools-more.js

105 ms

rokbox.js

rokbox.js

93 ms

bootstrap.min.js

bootstrap.min.js

92 ms

modal.js

modal.js

130 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

131 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

131 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

141 ms

mobile.js

mobile.js

141 ms

jeprettysmoothmenu.js

jeprettysmoothmenu.js

142 ms

main.css

main.css

150 ms

collect

collect

26 ms

js

js

195 ms

mqdefault.jpg

mqdefault.jpg

133 ms

mqdefault.jpg

mqdefault.jpg

138 ms

mqdefault.jpg

mqdefault.jpg

151 ms

mqdefault.jpg

mqdefault.jpg

143 ms

mqdefault.jpg

mqdefault.jpg

148 ms

mqdefault.jpg

mqdefault.jpg

140 ms

mqdefault.jpg

mqdefault.jpg

141 ms

mqdefault.jpg

mqdefault.jpg

147 ms

logo.png

logo.png

129 ms

icon_active.png

icon_active.png

130 ms

line.jpg

line.jpg

130 ms

facebook_aqu_24.png

facebook_aqu_24.png

130 ms

myspace_aqu_24.png

myspace_aqu_24.png

130 ms

twitter_aqu_24.png

twitter_aqu_24.png

129 ms

rss_aqu_24.png

rss_aqu_24.png

148 ms

homepage-logo.png

homepage-logo.png

163 ms

big_img_home.jpg

big_img_home.jpg

164 ms

yello-box.png

yello-box.png

149 ms

home-b.jpg

home-b.jpg

147 ms

video-img-botox.png

video-img-botox.png

197 ms

app-store.png

app-store.png

168 ms

google-play.png

google-play.png

170 ms

arrow.png

arrow.png

172 ms

main_img_home-arabic.jpg

main_img_home-arabic.jpg

201 ms

video-new-arabic.png

video-new-arabic.png

187 ms

0.jpg

0.jpg

88 ms

0.png

0.png

95 ms

1.jpg

1.jpg

108 ms

icon_facial.png

icon_facial.png

115 ms

2.jpg

2.jpg

137 ms

icon_breast.png

icon_breast.png

108 ms

3.jpg

3.jpg

114 ms

icon_injection.png

icon_injection.png

120 ms

4.jpg

4.jpg

126 ms

icon_body.png

icon_body.png

128 ms

videoicon.png

videoicon.png

132 ms

bg_n.png

bg_n.png

133 ms

bg_ne.png

bg_ne.png

144 ms

bg_e.png

bg_e.png

146 ms

bg_se.png

bg_se.png

149 ms

bg_s.png

bg_s.png

158 ms

bg_sw.png

bg_sw.png

156 ms

bg_w.png

bg_w.png

154 ms

bg_nw.png

bg_nw.png

161 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

70 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

80 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

81 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf

82 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

81 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

82 ms

all.js

all.js

17 ms

closebox.png

closebox.png

140 ms

all.js

all.js

8 ms

38 ms

Accessibility Review

nadersaab.com accessibility score

74

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.

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

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

nadersaab.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nadersaab.com SEO score

85

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

High

Tap targets are not sized appropriately

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

nadersaab.com

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