Tools & Wizards About Us
naji-imam.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

naji-imam.com

ناجي محمد الإمام

Page Load Speed

6.2 sec in total

First Response

1.6 sec

Resources Loaded

3.8 sec

Page Rendered

848 ms

naji-imam.com screenshot

About Website

Visit naji-imam.com now to see the best up-to-date Naji Imam content and also check out these interesting facts you probably never knew about naji-imam.com

مفكر وشاعر موريتاني , ناجي محمد الإمام , شعر , أدب , رواية

Visit naji-imam.com

Key Findings

We analyzed Naji-imam.com page load time and found that the first response time was 1.6 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

naji-imam.com performance score

0

Network Requests Diagram

naji-imam.com

1596 ms

all.js

26 ms

analytics.js

25 ms

style.css

160 ms

font.css

1205 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 90% of them (90 requests) were addressed to the original Naji-imam.com, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Naji-imam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (42%)

Content Size

4.1 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Naji-imam.com main page is 4.1 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. 65% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 73.5 kB

  • Original 89.2 kB
  • After minification 76.0 kB
  • After compression 15.7 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 13.2 kB, which is 15% 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 73.5 kB or 82% of the original size.

Image Optimization

-35%

Potential reduce by 1.1 MB

  • Original 3.2 MB
  • After minification 2.1 MB

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, Naji Imam needs image optimization as it can save up to 1.1 MB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 401.2 kB

  • Original 647.9 kB
  • After minification 620.5 kB
  • After compression 246.6 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 401.2 kB or 62% of the original size.

CSS Optimization

-87%

Potential reduce by 107.4 kB

  • Original 123.8 kB
  • After minification 99.0 kB
  • After compression 16.4 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. Naji-imam.com needs all CSS files to be minified and compressed as it can save up to 107.4 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (48%)

Requests Now

98

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

naji-imam.com

naji-imam.com

1596 ms

all.js

all.js

26 ms

analytics.js

analytics.js

25 ms

style.css

style.css

160 ms

font.css

font.css

1205 ms

nextgen_gallery_related_images.css

nextgen_gallery_related_images.css

249 ms

css-front.css

css-front.css

240 ms

styles.css

styles.css

243 ms

styles-rtl.css

styles-rtl.css

249 ms

style.css

style.css

251 ms

sidebar-login.css

sidebar-login.css

322 ms

postratings-css.css

postratings-css.css

309 ms

postratings-css-rtl.css

postratings-css-rtl.css

329 ms

pagenavi-css.css

pagenavi-css.css

330 ms

mootools-1.2.4-core-yc.js

mootools-1.2.4-core-yc.js

442 ms

swfobject.js

swfobject.js

430 ms

jquery.js

jquery.js

543 ms

jquery-migrate.min.js

jquery-migrate.min.js

438 ms

ajax.js

ajax.js

424 ms

superb-slideshow.js

superb-slideshow.js

514 ms

blockui.min.js

blockui.min.js

514 ms

sidebar-login.min.js

sidebar-login.min.js

512 ms

mediaboxAdvBlack.css

mediaboxAdvBlack.css

542 ms

mediaboxAdv-1.2.0.js

mediaboxAdv-1.2.0.js

596 ms

shutter-reloaded.css

shutter-reloaded.css

599 ms

BrowserPreview_tmp1.gif

BrowserPreview_tmp1.gif

812 ms

logo.png

logo.png

666 ms

naji.png

naji.png

688 ms

%D9%86%D8%A7%D8%AC%D9%8A-1.png

%D9%86%D8%A7%D8%AC%D9%8A-1.png

1071 ms

%D9%86%D8%A7%D8%AC%D9%8A-2.png

%D9%86%D8%A7%D8%AC%D9%8A-2.png

1090 ms

%D9%86%D8%A7%D8%AC%D9%8A-%D9%85%D8%AD%D9%85%D8%AF-%D8%A7%D9%84%D8%A5%D9%85%D8%A7%D9%85.png

%D9%86%D8%A7%D8%AC%D9%8A-%D9%85%D8%AD%D9%85%D8%AF-%D8%A7%D9%84%D8%A5%D9%85%D8%A7%D9%85.png

1172 ms

7.png

7.png

1178 ms

6.png

6.png

1137 ms

5.png

5.png

1658 ms

enfants-nomades.jpg

enfants-nomades.jpg

1179 ms

%D8%AC%D9%85%D8%A7%D9%84.jpg

%D8%AC%D9%85%D8%A7%D9%84.jpg

1216 ms

Adrar2.jpg

Adrar2.jpg

1248 ms

Azba01.jpg

Azba01.jpg

1282 ms

%D8%B4%D8%B9%D8%A7%D8%B1-%D8%A7%D9%84%D8%B6%D8%A7%D8%AF.jpg

%D8%B4%D8%B9%D8%A7%D8%B1-%D8%A7%D9%84%D8%B6%D8%A7%D8%AF.jpg

1256 ms

collect

collect

14 ms

collect

collect

10 ms

js

js

37 ms

170 ms

shutter-reloaded.js

shutter-reloaded.js

1239 ms

xd_arbiter.php

xd_arbiter.php

27 ms

xd_arbiter.php

xd_arbiter.php

38 ms

fonts.css

fonts.css

1191 ms

jquery-1.6.4.min.js

jquery-1.6.4.min.js

1253 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

1249 ms

jquery.tools.min.js

jquery.tools.min.js

1272 ms

effects.js

effects.js

1243 ms

jquery.tweet.js

jquery.tweet.js

1307 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

1237 ms

jquery.tipsy.js

jquery.tipsy.js

1234 ms

jquery.imgr.min.js

jquery.imgr.min.js

1242 ms

jcarousellite_1.0.1.pack.js

jcarousellite_1.0.1.pack.js

1249 ms

custom.js

custom.js

1187 ms

top.js

top.js

1200 ms

jquery.carouFredSel-5.0.6-packed.js

jquery.carouFredSel-5.0.6-packed.js

1190 ms

%D8%AF%D8%A7%D9%84%D9%8A%D8%A9.jpg

%D8%AF%D8%A7%D9%84%D9%8A%D8%A9.jpg

1280 ms

BrowserPreview_tmp1.gif

BrowserPreview_tmp1.gif

1395 ms

attm.png

attm.png

1176 ms

%D9%85%D8%B3%D8%A7%D8%AD%D8%A9-%D8%A7%D8%B9%D9%84%D8%A7%D9%86%D9%8A%D8%A9.jpg

%D9%85%D8%B3%D8%A7%D8%AD%D8%A9-%D8%A7%D8%B9%D9%84%D8%A7%D9%86%D9%8A%D8%A9.jpg

1186 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

372 ms

body.png

body.png

352 ms

header.png

header.png

385 ms

topNav.png

topNav.png

385 ms

headerBg.png

headerBg.png

423 ms

twitter.png

twitter.png

417 ms

facebook.png

facebook.png

424 ms

rss.png

rss.png

425 ms

sliderBg.png

sliderBg.png

431 ms

right.png

right.png

499 ms

left.png

left.png

498 ms

standard.png

standard.png

495 ms

dateBg.png

dateBg.png

497 ms

commentsBig.png

commentsBig.png

499 ms

postDetailsBg.png

postDetailsBg.png

558 ms

admin_user_2.png

admin_user_2.png

568 ms

Paperclip.png

Paperclip.png

589 ms

Graph.png

Graph.png

565 ms

widgetSeperator.png

widgetSeperator.png

586 ms

Document.png

Document.png

525 ms

GE_SS_Two_Bold.woff

GE_SS_Two_Bold.woff

560 ms

close.gif

close.gif

621 ms

prev.gif

prev.gif

585 ms

prev-d.gif

prev-d.gif

573 ms

next.gif

next.gif

565 ms

next-d.gif

next-d.gif

549 ms

resize1.gif

resize1.gif

559 ms

resize2.gif

resize2.gif

558 ms

resize-d.gif

resize-d.gif

533 ms

ping

ping

169 ms

loading.gif

loading.gif

490 ms

footerBg.png

footerBg.png

491 ms

Map.png

Map.png

526 ms

Link.png

Link.png

519 ms

Cog.png

Cog.png

516 ms

pagerActive.png

pagerActive.png

502 ms

pager.png

pager.png

502 ms

SEO Factors

naji-imam.com SEO score

0

Language and Encoding

  • Language Detected

    AR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Naji-imam.com can be misinterpreted by Google and other search engines. Our service has detected that Arabic 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 Naji-imam.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

naji-imam.com

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