Seguro Directo is a Portuguese automobile insurance company member of the Ageas Group and was established in 1996. This project's goal was to replace their (really) aged website, improving not only the visual aspect but also the insurance simulation experience.
My role
This was my first big project and one that I worked on from its beginning to its conclusion. I was not the main Frontend developer but that didn't stop me from giving my inputs and approaching each challenge in my own way.This project had a different workflow when compared to our usual one at Fullsix though since the backend was the clients' responsibility. Furthermore, the client requested me and another Frontend developer to move to their office until the project finished, which resulted in daily communication with them, not only in UI feedbacks but also in backend integration.I'm happy with the result since it was, as I said above, my first big project and therefore a huge learning experience. There were ups and downs through it and it was not easy having to rellocate to the clients' headquarters but I am proud of what the website turned out to be, especially with its complex simulation flow.Regarding the code, it was mostly written in jQuery with a few plugins like slick.js, selectize.js, bodymovin.js and a few others. We used Sass for the styling and pure HTML for the content, getting our code compiled by Gulp. Internet Explorer 10 and 11 had to be supported, as well as every other major browser.
Responsive development
Lighthouse results
Lighthouse is an open-source, automated tool created by
Google for improving the quality of web pages. It runs a
series of audits that generate a report indicating where and
how to improve your page/website. It audits Performance
(page speed), Accessibility (for invisuals using screen
readers for example), Best Practices (general development
practices) and SEO (search engine optimization)
Since I only had control over the frontend, I was a bit limited on the possible improvements. I can't control the images sizes (which usually takes a huge toll in performance and is the case here) or any of the backend behavior. The best I could do was write efficient JavaScript and CSS, write semantic HTML with no unnecessary tags and not use JavaScript plugins that weren't needed.
35
Performance
60
Accessibility
75
Best Practices
100
SEO
More pages
Credits
Frontend - André Marques, Paulo Garcia, Pedro Duarte, Ricardo Melo & Jorge Chagas