Transitioning to Local CDN for Fonts

We're excited to announce an update to our website's font delivery system. In our ongoing efforts to enhance performance, security and user experience, we've made the decision to transition from relying on Google Fonts to hosting our fonts locally on our own Content Delivery Network (CDN).

 

What's changing...

Local Hosting: Instead of fetching fonts from external servers such as Google Fonts, we're now storing our font files directly on our own CDN infrastructure.

Improved Performance: By hosting fonts locally, we reduce reliance on external servers, resulting in faster load times and a smoother browsing experience for our users.

Enhanced Security: With fonts hosted on our own CDN, we have greater control over security measures, ensuring that font files are delivered securely to our users.

Reduced Dependency: Moving away from external font providers minimises the risk of service disruptions or changes from third-party providers, providing greater stability for the MyCompliance platform.

 

What you need to know...

Default font changes to Email Templates, Phish Templates and Learning Experiences

To ensure consistency, we have changed the default fonts that we will be using across our email and phish templates as well as our Learning Experiences.

In some email templates, you may notice some small cosmetic changes to the default fonts being used; however, the content and layout of our email and phish templates and our Learning Experiences remains unchanged.

Note: If you have used the email editor to change the font being used, this will remain unchanged.

 

Seamless transition of fonts on the MyCompliance platform: Users should experience a seamless transition, with no action required on their part. Fonts will continue to render as usual, but with the added benefits of improved performance and security.

 

If you encounter any issues related to this update, please don't hesitate to reach out to support@metacompliance.com.

Back to all articles