diff --git a/README.md b/README.md index fbb5e9d..ce70ee3 100644 --- a/README.md +++ b/README.md @@ -22,10 +22,12 @@ PicturePolyfill is fast and easy to use because: picturePolyfill is better than picturefill because: -* it's **15x faster** on IE 10, **8x faster** on mobile Safari, **6x faster** on Firefox and Safari, **4x faster** on Chrome and Opera [see performance test](http://jsperf.com/picturepolyfill-204-vs-picturefill-121-performance-test) * it uses the **real `picture` markup** +* it's **15x faster** on IE 10, **8x faster** on mobile Safari, **6x faster** on Firefox and Safari, **4x faster** on Chrome and Opera [see performance test](http://jsperf.com/picturepolyfill-300-vs-picturefill-121-performance-test/2) +* it **better handles AJAX calls** because it lets you parse only a section of your DOM, passing the parent element to the `parse` method * it gives you the ability to **choose a default image** that you want to show on Internet Explorer desktop, without the need to add any comment -* it's **solid**, since `picturePolyfill` code is test driven with full code coverage +* it's **solid**, since its code is all covered by tests + ## Markup pattern and explanation diff --git a/performance/picturefill_vs_picturePolyfill_v3.0.0.html b/performance/picturefill_vs_picturePolyfill_v3.0.0.html new file mode 100644 index 0000000..bab8784 --- /dev/null +++ b/performance/picturefill_vs_picturePolyfill_v3.0.0.html @@ -0,0 +1,47 @@ + + +
+This test is published in jsPerf: picturePolyfill 3.0.0 vs picturefill 1.2.1 performance test
+ +See picturePolyfill GitHub repo page and online DEMO.
+ + + + + + + + + + + + + + + \ No newline at end of file