Performances 2017

Does size really matter?

YES

GT Metrix

A tool for...

Dareboost

A tool for...

4 "toys" to improve perfs

Webpack bundle analyzer

A tool for...

JSCPD

A tool for...

Title Text

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi nec metus justo. Aliquam erat volutpat.

Strengths

• no duplicate code (less than 2%)
• very maintainable/scalable tools (npm, angular, TS, scss, node, mysql) with big communities

Weaknesses 

• bundles too big
• files too big
• too much files

SWOT tactical approach

Opportunities

• A project to discover the very new techs
• A CMS that could become a basis for other project in the company

threats

• no real control on SEO
• app slower and slower
• a lot of parts without control (bearstech, appsmiles, etc.)

Reduce bundle size

• no more global import (@see rxjs 600kb vs rxjs/Observable 80kb)
• update packages ! (@angular/cli 1.2.6 produce a bundle 200kb lighter)
• Reference only minified script (tinycme 1.6mb to 0.45mb...)
• Find a solution for external library not used everywhere (tinymce ?)

Files too big

• optimize every images (200kb to 50kb for the sam result
• optimize scss (no big nesting (<3), maximize mutualization

Fight weaknesses

Too much files

• use dedicated tool .angular-cli.json (braintree ?)

SEO

• ...

Keep control

• ...

Fight threaten

App slower over time

• constructor for dependencies, ngOnInit for initialization
• user the router loadChildren practice  (@see https://toddmotto.com/angular-component-router)