Online Resource

Online Resource

Online Resource

Online Resource

Dewey Library - QH331.E85 2018

Online Resource

Online Resource

Online Resource

Hayden Library - QH319.A1 L36 2018

Dewey Library - QH332.B25 2019

Online Resource

Dewey Library - QH501.D38 2019

Dewey Library - QH438.7.B38 2019

Hayden Library - QH450.B34 2018

Across several presentations at Google Conversions in Dublin, several speakers shared insights and best practices for conversion rate optimization. Here's a few highlights:

Confirmation Bias - Michael Aagaard

• In the 18th century, tobacco smoke was considered very good for your heart and lungs. In particular tobacco enemas were quite popular so much that they were placed along the banks of the river Thames to help drowning victims. This is an example of confirmation bias at work.
• Confirmation biases is our tendency to accept evidence we agree with at face value and dismiss information we don't agree with unless the evidence is overwhelming. Confirmation biases limits our ability to seek out and uncover the truth.
• Torturing data: if you torture any data long enough it will confess to anything. High levels of correlation between things don't imply causation. We have to be careful to not see what we want in data.
• Stopping A/B tests when they show the impact we want is an example of confirmation bias. Instead, let them run for an appropriate amount of time. Over time, tests are likely to show much less effects.
• How to overcome confirmation bias: accept the fact that you could be wrong, seek out a different perspective. Find people who talk to customers/users. They have a bias toward end users.
• Don't test your ideas, do detective work to find out what customers need and how they talk about it. Then your A/B test is simply the final test at the end to see if you did your detective work well.

CRO - Lina Hansson

• Celebrate the discovery of weak spots. Don't take it as failure but instead be happy when you find something that can be improved.
• The biggest missed opportunity in conversion rate optimization is usability testing. Move away from opinions and instead use user testing to identify issues.
• A common pain point across retail sites is find-ability: both search and browse. When we move to mobile, many sites remove their top categories list in order to fit on smaller screens. This creates discoverability issues. One of the first things retail sites should test is adding categories visibly on their home page.
• Value propositions for companies are usually cut for mobile. Instead of removing them, redesign them to make them work on mobile.
• People can be classified into four behavior types. Methodical people read completely and analyze before making decisions. Humanistic people react strongly to the opinions of others. Competitive people move quickly and expect things to work. Spontaneous people are emotional and fast-paced. You can design experiences that are appropriate for each of these behavior types.
• The companies that solve checkout on mobile are the ones that will win.

Meaningful Data - Simo Ahava

• It's quite simple to get a service like Google Analytics set up but how do we use these tools to really understand what we're doing. How can data become meaningful?
• Tactics (tool expertise) without a strategy (business expertise) are just party tricks and a strategy without tactics is just talk. What brings the two together is agility.
• Tools must be customized for your organization's needs. We are not trying to optimize metrics but our businesses. Default metrics and reports need to be adjusted to work with your specific needs.

Landing Pages - Anna Potanin

• Designers want to do their best and create unique interfaces but making things for the Web often requires understanding and using conventions. Only apply a unique visual design after you have followed best practices.
• 3 things all retail sites should have on their landing and home pages: call to action, value propositions, and visuals.
• The more prominent you make your search bar, the more searches you get. Why do you want to do this? Conversion rates are usually much higher for people who search

In his Move Fast and Don’t Break Things presentation at An Event Apart in Seattle, Scott Jehl shared a number of resilient patterns and tools to help us establish and maintain performant access to our Web sites. Here's my notes from his talk:

• For successful Web design, people used to suggest we move fast and break things. Today we've become more responsible but things can still break for our users if we're not mindful.
• So many factors that can compromise the delivery of our Web sites are out of our control. We need to be aware of these in order to build resilience into our designs.
• We used to use browser detection and feature detection to ensure our sites were supported across Web browsers. Progressive enhancement's importance ballooned as a wide range of new devices for accessing the Web, touch interactions, and more browsers became popular.
• Trying to make a Web site look and work the same across devices was broken, we realized this was the wrong goal and we need to adapt to varying screens, networks, input types, and more.
• Some practices stay good. Progressive enhancement and accessibility prepared us for many of these changes but it is also a performance enhancement on its own.
• Figuring out how to make Web sites faster used to be hard but the tools we have for measuring performance have been improving (like PageSpeedTest and WebPageTest).

Making Web Sites Fast

• First meaningful content: how soon does a page appear to be useful to a user. Progressive enhancement is about starting with meaningful HTML and then layering additional enhancements on top of it. When browsers render HTML, they look for dependencies in the file (CSS and Javascript) before displaying anything.
• CSS and Javascript are most often the render-blockers on sites, not images & videos. Decide if they need to load at high priority and if not, load async or defer. If you need them to run right away, consider server push (HTTP2) to send files that you know the browser needs making them ready to render right away.
• If your server does not support push, you can inline your critical CSS and/or Javascript. Inlining however is bad for caching as it does not get reused by other pages. To get around this you can use the Cache API to inline content and cache it as a file for reuse.
• Critical CSS tools can look over a series of files and identify the common CSS you need across a number of different pages for initial rendering. If you inline your critical CSS, you can preload the rest of your CSS (not great browser support today).
• Inlining and push are best for first time visits, for return visits they can be wasteful. We can use cookies for checking for return visits or make use of Service Worker.
• Time to interactive: time it takes a site to become interactive for the user. We should be aiming for interactivity in under 5seconds on a median mobile phone on 3G. Lower end phones can take a long time to process Javascript after it downloads.
• More weight does not mean more wait. You can prioritize when things load to make pages render much faster.

Keeping Web Sites Fast

• Making a web site fast is easier than keeping it fast. Over time, Web sites will add a number of third party services with unknown performance consequences.
• We can use a number of tools, like Lighthouse, to track performance unfriendly dependencies. Speed Curves will let you set performance budgets and see when things are over. This allows people to ask questions about the costs of what we're adding to sites.
• Varying content and personalization can increase optimizations but they are costly from a performance perspective since they introduce a second meaningful content render. Moving these features to the server-side can help a lot.
• Cloudflare has a solution that allows you to manipulate pages on their server before it comes down to browser. These server-side service workers allow you to adjust pages off the client and thereby avoid delays.
• Homepages and landing pages are often filled with big images and videos. They're difficult to keep performant because the change all the time and are often managed outside of a central CMS.
• For really image heavy pages, we can use srcset attributes to define multiple sizes of images. Writing this markup can be tricky if written by hand. Little helper apps can allow people to write good code.
• Soon we'll have a native lazy load feature in browsers for images and iframes. Chrome has it in testing now and can send aspect ratios before actual images.

In his Third-Party Software and the Fate of the Web presentation at An Event Apart in Denver, Trent Walton talked through the impact of third party scripts on Web sites and how to ensure they don't degrade performance and user experience. Here's my notes from his talk:

• With most client work, no one is paying attention to the impact of third parties on Web sites.
• Third parties are requests on a Web page coming from an external URL. Examples: TypeKit, Google Analytics, etc. People use third parties to get data to make product decisions, earn income (ads, marketing), add content (videos, fonts), add functionality (comments, chat, etc.).
• But third parties can also create issues. Loading scripts and files can really slow things down or provide an inconsistent UI and create privacy issues based on how they handle user data.
• If you care about the final deliverable for a Web site, you need to be aware of the impact of third parties on your product. All the work we do on optimizing images, code, and designs can be quickly outweighed by the addition of third party scripts to a site.
• Starting with the categories of 3rd party scripts helps you get a good sense of why people are using them: Advertising, A/B testing Tools, Analytics, Social Media, CDN, Customer Interaction, Comments, Essential.
• Looking at the top third party requests across the Alexa top 46 sites in the United States shows 213 different domain sources. The average site has 22 different domains. News sites have the most third party domains.
• Several tools can help you understand what's happening with third party scripts on a site. Request Map Generator can help you create a visualization of the different third parties on your Web site to help create awareness of what's happening on your site. Chrome's Lighthouse tool has a similar set of capabilities.
• How do third parties impact end users? Does your site depend on third parties to function? As more people block these components, will it break? Re-marketing can create creepy experiences as content begins "follow" you online.
• Web builders are on the front lines. We can advocate for the right approaches to privacy and data management. Though some of these conversations may be hard, it's our responsibility to end users.
• Web browsers now have tools to help you manage third party scripts like cookies and cross-site tracking. But most people are likely not turing on the stricter versions of these features.
• If you control a site, you can decide what third parties you want to include. But what about sites you don't control? Consider the perspective of your clients/companies and present data that explains the impact of third party on conversion and user experience.
• Establish some standards for third party integrations: determine the value, avoid redundant services, work with a performance budget, comply with privacy policies.
• Audit the third parties on your site and include data that illustrates how they perform against your standards. Compare this audit to competitors in order to set benchmarks or comparisons.
• Get specific insights: there's usually a few instances of third parties that have become redundant, unnecessary, or are blocking page rendering. These wins create credibility and illustrate impact.
• Maintain ongoing conversations with teams to make effective decisions about third parties on your sites.

How H&M, Zara and Marks & Spencer are buying viscose from highly polluting factories in Asia. By Natasha Hurley.

He puts his life on the line to protect the Democratic Republic of Congo's national parks.

KidZania is an unashamed shrine to the sterile, dystopian human-made landscapes, comedian Steve Parry writes.

And she has blamed the 'growing Indian and Chinese appetite in contributing to the global food crisis'. The US Secretary of State is technically correct since both the countries dominate the world food consumption. But analysts feel she is morally and socially wrong.

According to USDA estimates, the US accounted for an average of 11.5 percent of world exports of rice for calendar years 2004 through 2007 and is projected at 12.7 percent for 2008. US exports will increase to 3.5 million metric tons while world total exports decline to 27.5 MMT. The largest rice exporter is Thailand at 9.0 MMT for 2007/08, 32.7 percent of world exports, down 0.5 MMT from 2006/07 and up from 7.3 MMT in 2004/05 and 2005/06.

Among large banks, the brokerage sees ICICI Bank's PAT declining 49 per cent QoQ to Rs 2,100 crore in Q4FY20, followed by a 68 per cent sequential decline in Axis Bank's PAT at Rs 564.6 crore.

It had reported a pre-tax profit of Rs 8,954.38 crore in the same period last financial year (Q4FY19).

The company's total income fell to Rs 6,327.57 crore in the quarter from Rs 8,077.89 crore in the year-ago period

The Pune-headquartered company reported Rs 804 crore in consolidated net profit for the March quarter (Q4FY20), a decline of 29.1 per cent on year-on-year (YoY) basis

Explore CT's special issue for the Easter season.

New York : Teachers College Press, ©2001

London ; New York : Bloomsbury Academic, 2018

Toronto ; Vancouver : Canadian Scholars, 2019.

New Brunswick : Rutgers University Press, [2019]

London : Routledge, 2017.

Edmonton, Alberta : Brush Education Inc., 2020

Dordrecht, Netherlands : Springer, ò007

Berlin ; New York : Springer, [2007]

Dordrecht, the Netherlands : Springer, [2007]

Dordrecht : Springer, 2006

Tyson Foods, Inc., a Rogers, Ark. establishment, is recalling approximately 69,093 pounds of frozen, ready-to-eat chicken strip products that may be contaminated with extraneous materials, specifically pieces of metal.

Tyson Foods, Inc., a Rogers, Ark. establishment, is recalling approximately 11,829,517 pounds of frozen, ready-to-eat chicken strip products that may be contaminated with extraneous materials, specifically pieces of metal.

Conagra Brands, Inc., a Russellville, Ark. establishment, is recalling approximately 2,094,186 pounds of frozen entrees due to misbranding and an undeclared allergen.

Abingdon, Oxon : Radcliffe Publishing Ltd, [2011]

Seyssel : Champ Vallon, [2013]

Turnhout, Belgium : Brepols, [2018]