Skip to content

Commit

Permalink
fix(blog): Emphasis of 2 words in Content Mesh Pt. 4 (#11064)
Browse files Browse the repository at this point in the history
Spotted these while re-reading [Journey to the Content Mesh Part 4: Why Mobile Performance Is Crucial](https://www.gatsbyjs.org/blog/2018-10-16-why-mobile-performance-is-crucial/):

<img width="804" alt="foo" src="https://user-images.githubusercontent.com/21834/51130018-43679400-182c-11e9-80c5-d454cf0aad06.png">
  • Loading branch information
fk authored and DSchau committed Jan 14, 2019
1 parent 2db49e8 commit ad6a8cf
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -148,7 +148,7 @@ Among the many implementation challenges are:

Web performance is critical for retaining and engaging users, especially on mobile. If [every 100ms of latency costs 1% of sales](https://www.digitalrealty.com/blog/the-cost-of-latency/), reducing average page load times from 5 seconds to 1-2 seconds could generate 30-40% more sales.

But just because performance is the *right *thing doesn’t make it the _easy_ thing. Implementing performance optimizations on a _per-site basis_ is often *difficult *and _costly_.
But just because performance is the _right_ thing doesn’t make it the _easy_ thing. Implementing performance optimizations on a _per-site basis_ is often _difficult_ and _costly_.

To overcome these obstacles, high-performing website teams should look to a content mesh that bakes in performance on a _framework_ level.

Expand Down

0 comments on commit ad6a8cf

Please sign in to comment.