Marfeel is keenly aware that to remain competitive and maximize the revenue generated per visit, publishers require the most technically innovative systems to deliver their content with the industry-leading speed and smoothness Marfeel is known for. 

For this reason, Marfeel uses Fastly as their CDN (Content Delivery Network); a move that proves Marfeel is committed to taking the mobile web to the next level and delivering the industry's cutting edge tech in the process. With the massive deal signed with Fastly, Marfeel now uses the same CDN as some of the world's largest publishers and content providers including the New York Timesthe GuardianBuzzfeedPinterestWenner MediaWired, Twitter, Airbnb, and Github


Marfeel's decision to use Fastly - one of the ten fastest growing B2B companies of the last 30 years - empowers publishers with a network of servers referred to as points of presence (POP), all over the world. This global network of servers ensures that a publisher's content is delivered as close to their audience as possible at optimal speed, regardless of their global location. 

For a comprehensive overview of Fastly's network map and strategic points of presence locations across the globe to deliver Marfeel's blazing speed, see the Fastly POP locations article.

Using the Fastly CDN also positions Marfeel with another tech leader that serves over 10% of all internet requests (400 billion a day) with 17.5 Tbps of connected global capacity (the equivalent of 14 billion simultaneous text messages).

How a partner's content is delivered

When a user requests a partner's content through a mobile device, the request is directed to the nearest point of presence or POP. 

POPs cache content according to hot traffic and essentially deliver a copy of the publisher's content to their reader. This is so the request doesn't have to make a round-trip to the origin server, which heavily reduces latency and contributes to Marfeel's industry-leading page speed. Fastly also allows the use of origin shields to further limit the amount of requests that need to go to origin servers.  

In the rare case that there isn't any cached content due to a lack of traffic, the request is redirected. This normally only happens when a partner has just gone live or is viewing a demo as illustrated in the GoLive and Demo Speeds article.

For a detailed explanation of how Fastly delivers content, see the How Fastly's CDN Service works article in the Fastly documentation


The following are just a few of the features that Marfeel partners enjoy when they activate their Marfeel solution:


To fully leverage the capability of this CDN, Marfeel uses HTTP/2 to optimize their first render and consistently load the first meaningful paint in under a second, further boosting the remarkable speed and smoothness Marfeel is synonymous with.

Marfeel also enhances its use of HTTP/2 with server push which pre-emptively sends responses to a client and conserves round trips to the origin server. For more information, see the Optimizing HTTP/2 server push with Fastly article.

Static content 

Marfeel's CDN is especially adept at caching static content like images, JavaScript, and CSS with better cache hit ratios and quicker response times. Fastly also boasts support for stale-while-revalidate to make serving even more reliable.  

Origin shield

With Fastly's origin shield, only one connection hits the publisher's origin, considerably reducing saturation at the origin and providing economy at scale. A by-product of this is a significantly reduced cost for a publisher to upkeep their infrastructure. 

World-class DDoS

Fastly maintains world-class DDoS (distributed denial-of-service) protection. This means publishers will never be hit by DDoS attacks because Fastly's cutting-edge technology protects origins through sophisticated techniques like edge filtering and origin cloaking


For publishers that serve their content over HTTPS, Marfeel's CDN delivers an optimized SSL handshake based on TLS 1.4.


For more details regarding Fastly's features and offer, see the Fastly documentation