Tools & Wizards About Us
iamnguele.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

iamnguele.com

Coding Nagger - Jean-Dominique Nguele: Writer of Code - Blogger - Podcast host - Not listed in Forbes' 30 under 30.

Page Load Speed

7.1 sec in total

First Response

285 ms

Resources Loaded

5.7 sec

Page Rendered

1.1 sec

iamnguele.com screenshot

About Website

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

Jean-Dominique Nguele the Coding Nagger is a Writer of Code definitely not listed in Forbes' 30 under 30. He writes blog posts and also this description despite it being third person. You will fi...

Visit iamnguele.com

Key Findings

We analyzed Iamnguele.com page load time and found that the first response time was 285 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

iamnguele.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value9,310 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

iamnguele.com

285 ms

www.codingnagger.com

2880 ms

wp-emoji-release.min.js

236 ms

style.min.css

263 ms

ef20a.css

413 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Iamnguele.com, 32% (19 requests) were made to Codingnagger.com and 15% (9 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Codingnagger.com.

Page Optimization Overview & Recommendations

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

Content Size

683.5 kB

After Optimization

571.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 67.2 kB

  • Original 82.2 kB
  • After minification 82.2 kB
  • After compression 15.0 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 67.2 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 43.2 kB

  • Original 463.2 kB
  • After minification 420.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. Iam Nguele images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.2 kB

  • Original 67.9 kB
  • After minification 67.8 kB
  • After compression 66.7 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

-1%

Potential reduce by 707 B

  • Original 70.2 kB
  • After minification 70.2 kB
  • After compression 69.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. Iamnguele.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (65%)

Requests Now

48

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iam Nguele. 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 from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

iamnguele.com

iamnguele.com

285 ms

www.codingnagger.com

www.codingnagger.com

2880 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

236 ms

style.min.css

style.min.css

263 ms

ef20a.css

ef20a.css

413 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

348 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

367 ms

3400b.css

3400b.css

464 ms

a30b6.css

a30b6.css

528 ms

css

css

400 ms

27435.css

27435.css

605 ms

jetpack.css

jetpack.css

334 ms

jquery.min.js

jquery.min.js

333 ms

jquery-migrate.min.js

jquery-migrate.min.js

342 ms

3031a.js

3031a.js

519 ms

f32c4.js

f32c4.js

518 ms

embed.js

embed.js

396 ms

01027.css

01027.css

513 ms

87fac.css

87fac.css

546 ms

photon.min.js

photon.min.js

304 ms

86e9b.js

86e9b.js

1040 ms

3560d.js

3560d.js

1040 ms

eu-cookie-law.min.js

eu-cookie-law.min.js

327 ms

twitter-timeline.min.js

twitter-timeline.min.js

348 ms

673b0.js

673b0.js

1039 ms

e04a9.js

e04a9.js

1729 ms

e-202240.js

e-202240.js

359 ms

1615d.js

1615d.js

1058 ms

pexels-alexandro-david-1835016.jpg

pexels-alexandro-david-1835016.jpg

1373 ms

codingnaggercoding.png

codingnaggercoding.png

1767 ms

pmOS-nordVPN.png

pmOS-nordVPN.png

1016 ms

pexels-mikhail-nilov-7672255.jpg

pexels-mikhail-nilov-7672255.jpg

1387 ms

image-4.png

image-4.png

1307 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

404 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

639 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

931 ms

fa-brands-400.woff

fa-brands-400.woff

569 ms

fa-solid-900.woff

fa-solid-900.woff

640 ms

fa-regular-400.woff

fa-regular-400.woff

401 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

930 ms

fdc977a2-7fdb-4742-9944-d2104ca405db

fdc977a2-7fdb-4742-9944-d2104ca405db

927 ms

80db5440-b77e-4bc1-8206-31b0d677dfad

80db5440-b77e-4bc1-8206-31b0d677dfad

939 ms

278befb1-6999-4b51-b1f3-aeb4c9b763ea

278befb1-6999-4b51-b1f3-aeb4c9b763ea

977 ms

1_pay_mm_off.png

1_pay_mm_off.png

341 ms

widgets.js

widgets.js

626 ms

embed-46fee9e8d3c1218f3c86138f6c6c7a6f67389f8e31688acaebd6bff4ed925e9a.css

embed-46fee9e8d3c1218f3c86138f6c6c7a6f67389f8e31688acaebd6bff4ed925e9a.css

159 ms

image.png

image.png

259 ms

clamp-85d1f1841d156975509823b35c3521a104e0b831e8fe9e9d2a34b12c7f8dd24b.js

clamp-85d1f1841d156975509823b35c3521a104e0b831e8fe9e9d2a34b12c7f8dd24b.js

169 ms

credly-logo-gray-f59f823f945658eae89c152105e518c75b5b1ce51d4d8241ff73f33c1dd8f47d.svg

credly-logo-gray-f59f823f945658eae89c152105e518c75b5b1ce51d4d8241ff73f33c1dd8f47d.svg

75 ms

bceb8fa3-4221-4c11-b1cf-2ee473c5ef36

bceb8fa3-4221-4c11-b1cf-2ee473c5ef36

137 ms

0d900626-3155-4bac-a522-891c0a6a9394

0d900626-3155-4bac-a522-891c0a6a9394

143 ms

nr-943.min.js

nr-943.min.js

65 ms

widget_iframe.7dae38096d06923d683a2a807172322a.html

widget_iframe.7dae38096d06923d683a2a807172322a.html

133 ms

image.png

image.png

18 ms

azure-developer-associate-600x600.png

azure-developer-associate-600x600.png

42 ms

01577753b5

01577753b5

190 ms

01577753b5

01577753b5

176 ms

settings

settings

114 ms

01577753b5

01577753b5

115 ms

Accessibility Review

iamnguele.com accessibility score

84

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

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.

Best Practices

iamnguele.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

iamnguele.com SEO score

81

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

iamnguele.com

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