Your SlideShare is downloading. ×
0
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Taming 3rd party content
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Taming 3rd party content

1,107

Published on

Sergey Chernyshev presents about reducing the harm caused by these tools and best practices for consumers as well as creators of such 3rd party content.

Sergey Chernyshev presents about reducing the harm caused by these tools and best practices for consumers as well as creators of such 3rd party content.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,107
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Taming 3rd party content
  • 2. What's third party? "Loaded from another server..." - Sergey Chernyshev
  • 3. All over your site
  • 4. <script> Easy to integrate! Easy to update! Easy to grab user info!
  • 5. </script> Blocks rendering! Depends on their servers! Security & privacy risk!
  • 6. SLO-JS Single Line Of JavaScript
  • 7. Ads • Pay bills ($$$) • Chain of brokers • Rich (heavy) content • Need lots of user data
  • 8. Ads: how bad is it? • document.write (blocks, can't be post loaded) • Sometimes up to 7 nested wrappers, more then 20 requests • Fail rarely, but block the whole site
  • 9. Ads: Solutions! • Load after content is loaded • Use IFrames • Don't use 3rd party engines
  • 10. Widgets • Free content or functionality • Use JS for everything • Rarely cache • More complexity for your site
  • 11. Widgets: how bad? • Varies dramatically • Less reliable then ad networks
  • 12. Widgets: Solutions! • Find more static (or flash) version • Rewrite using their AJAX API • Use any API and assemble on back end, cache
  • 13. Trackers • Show what's going on • Need lots of user data • Delay load event (a little)
  • 14. Trackers: what to do? • Not so bad. Not much you can do either. • Use async version if exists (Google Analytics)
  • 15. When YOU develop widgets! • Don't use document.write! • HTML placeholder, async code & data • Cache JS code (in the browser) • Cache all or part of the data (know your TTLS) • Provide static alternative to SLO-JS (image / HTML to download / flash)

×