Why you should not use Angular for your frontend

With Angular you can create fancy-pancy beautiful functional super realtime sites.
But, the problem is, they don’t perform well.

I have a fairly well running website where I created a mobile only version using Angular und Angular Material.
It’s great when viewed on a smartphone or tablet. It has the same amount of ads as the server side rendered website.
However only 2 out of 1000 visitors are clicking ads and Adsense says that the “active view viewable” has only roughly 30%, but the SSR website has around 60%.
I’m using responsive adsense on the mobile site.
I’m also running a cache to deliver the pre-rendered website to search engines and other indexers.
The pre-rendering works that if a page is not in the cache, it’s getting fetched via chrome’s –dump-dom argument.
Search engines etc are receiving a pre-rendered document.
The SSR website has 3 times the visitors but roughly 750 clicks.
How can this be?
The only explanation I see is that the mobile layout is too clean and that ads are too obvious thus visitors aren’t clicking them. Those 5000 visitors can’t all be spiders.
How can an ads only be 30% viewable when it’s responsive? Most visitors are using iPhones. The viewports aren’t smaller than 350×50.

I don’t understand therefore I can only say to not use Angular as a frontend. It’s ok for configuration, where SEO and ads don’t matter. Writing a nice dashboard and entity manager etc.
Maybe some IOT Ux. But critical frontend is not one of Angular’s best places. Too bad because I really like it, but I think it’s better to fall back to what always worked.
And this is the so-called classic website, that is server side rendered, where templates are used and where ORMs make sense.

Spread the love

Leave a Reply

Your email address will not be published. Required fields are marked *