![]() ![]() I’m only really scratching the surface though, there’s some super interesting data on mobile and tablet render time too. #Fontforge faster turn off codeAll you have to do is setup some code similar to analytics, and the code is async’d in and the file is tiny, so no real impact on the site. BUT, in my graph I can see the Render time has some HUUGE spikes in it, one of them is 35 seconds long.Īs far as I’m aware this is the only tool I’ve ever used that actually gives me this sort of data so I thought I would share. Interestingly, overall my median page load is 1.4 seconds, which I am very happy about. I’ve had a couple hundred views now and I’m seeing some interesting data. It’s got wayyyyy better user experience tracking that GA (Google Analytics) because it was built specifically to measure what the user goes through. I’ve setup RUM (Real User Monitoring) at PingDom which is a front end user monitoring service. Or compromise with a well optimised, lightweight font stack (usually from Typekit), if we’re not using italics we don’t load italics! ” etc!!įor now if a client’s site is very speed dependant (hopefully backed up by solid analytics data and user research) I just use websafe fonts, boring but fast. Turns out if you use but don’t ever apply that font-family, the font won’t be downloaded. The first idea I saw was Dave Rupert’s tests on only loading on large screens. Dealing with this has been in the air recently so I thought I’d round up some of the ideas and add thoughts of my own. ![]() The issue is 1) custom fonts are awesome and we want to use them 2) custom fonts slow down our pages by being large additional resources. ![]()
0 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |