Skip to main content

Home/ @Publish/ Group items tagged Web

Rss Feed Group items tagged

Pedro Gonçalves

20 top web design and development trends for 2013 | Feature | .net magazine - 0 views

  • “If you’re designing a website and not thinking about the user experience on mobile and tablets, you’re going to disappoint a lot of users,” he warns. Designer Tom Muller thinks big brands getting on board will lead to agencies “increasingly using responsive design as a major selling point, persuading clients to future-proof digital marketing communications”. When doing so, Clearleft founder Andy Budd believes we’ll see an end to retrofitting RWD into existing products: “Instead, RWD will be a key element for a company’s mobile strategy, baked in from the start.” Because of this, Budd predicts standalone mobile-optimised sites and native apps will go into decline: “This will reduce the number of mobile apps that are website clones, and force companies to design unique mobile experiences targeted towards specific customers and behaviours.”
  • During 2012, the average site size crept over a megabyte, which designer/developer Mat Marquis describes as “pretty gross”, but he reckons there’s a trend towards “leaner, faster, more efficient websites” – and hopes it sticks. He adds: “Loosing a gigantic website onto the web isn’t much different from building a site that requires browser ‘X’: it’s putting the onus on users, for our own sakes.”
  • Designer and writer Stephanie Rieger reckons that although people now know “web design isn’t print,” they’ve “forgotten it’s actually software, and performance is therefore a critical UX factor”.
  • ...6 more annotations...
  • Bluegg studio manager Rob Mills reckons 2013 will see a “further step in the direction of storytelling and personality on the web, achieved through a greater focus on content and an increase in the use of illustration”.
  • Apps remain big business, but some publishers continue to edge to HTML5. Redweb head of innovation David Burton reckons a larger backlash is brewing: “The gold rush is over, and there’s unrest in that apps aren’t all they promised to be. We now live in a just-in-time culture, where Google can answer anything at the drop of a hat, and we no longer need to know the answers. The app model works the old way. Do we need apps for every brand we interact with? Will we even have iPhones in five years’ time? Who knows? But one thing is certain – the internet will remain, and the clever money is on making web apps that work across all platforms, present and future.”
  • Designer/developer Dan Eden says that with “more companies focussing web efforts on mobile,” designers will feel the pressure to brush up on the subject, to the point that in 2013, “designing for desktop might be considered legacy support”. Rowley agrees projects will increasingly “focus on mobile-first regarding design, form, usability and functionality”, and Chris Lake, Econsultancy director of product development, explains this will impact on interaction, with web designers exploring natural user interface design (fingers, not cursors) and utilising gestures.
  • We’re increasingly comfortable using products that aren’t finished. It’s become acceptable to launch a work-in-progress, which is faster to market and simpler to build – and then improve it, add features, and keep people’s attention. It’s a model that works well, especially during recession. As we head into 2013, this beta model of releasing and publicly tweaking could become increasingly prevalent.“
  • “The detail matters, and can be the difference between a good experience and a great experience.” Garrett adds we’ll also see a “trend towards not looking CMS-like”, through clients demanding a site run a specific CMS but that it not look like other sites using the system.
  • “SWD is a methodology for designing websites capable of being displayed on screens with both low and high pixel densities. Like RWD, it’s a collection of ideas, techniques, and web standards.”
Pedro Gonçalves

How Website Speed Actually Impacts Search Ranking - Moz - 0 views

  • in 2010, Google did something very different. Google announced website speed would begin having an impact on search ranking. Now, the speed at which someone could view the content from a search result would be a factor.
  • Google's Matt Cutts announced that slow-performing mobile sites would soon be penalized in search rankings as well.
  • While Google has been intentionally unclear in which particular aspect of page speed impacts search ranking, they have been quite clear in stating that content relevancy remains king.
  • ...13 more annotations...
  • When people say"page load time" for a website, they usually mean one of two measurements: "document complete" time or "fully rendered" time. Think of document complete time as the time it takes a page to load before you can start clicking or entering data. All the content might not be there yet, but you can interact with the page. Think of fully rendered time as the time it takes to download and display all images, advertisements, and analytic trackers. This is all the "background stuff" you see fill in as you're scrolling through a page.
  • Since Google was not clear on what page load time means, we examined both the effects of both document complete and fully rendered on search rankings. However our biggest surprise came from the lack of correlation of two key metrics! We expected, if anything, these 2 metrics would clearly have an impact on search ranking. However, our data shows no clear correlation between document complete or fully rendered times with search engine rank, as you can see in the graph below:
  • With no correlation between search ranking and what is traditionally thought of a "page load time" we expanded our search to the Time to First Byte (TTFB). This metric captures how long it takes your browser to receive the first byte of a response from a web server when you request a particular URL. In other words, this metric encompasses the network latency of sending your request to the web server, the amount of time the web server spent processing and generating a response, and amount of time it took to send the first byte of that response back from the server to your browser.
  • The TTFB result was surprising in a clear correlation was identified between decreasing search rank and increasing time to first byte. Sites that have a lower TTFB respond faster and have higher search result rankings than slower sites with a higher TTFB. Of all the data we captured, the TTFB metric had the strongest correlation effect, implying a high likelihood of some level of influence on search ranking.
  • The surprising result here was with the the median size of each web page, in bytes, relative to the search ranking position. By "page size," we mean all of the bytes that were downloaded to fully render the page, including all the images, ads, third party widgets, and fonts. When we graphed the median page size for each search rank position, we found a counterintuitive correlation of decreasing page size to decreasing page rank, with an anomalous dip in the top 3 ranks.
  • We suspect over time, though, that page rendering time will also factor into rankings due to the high indication of the importance of user experience.
  • our data shows there is a correlation between lower time-to-first-byte (TTFB) metrics and higher search engine rankings. Websites with servers and back-end infrastructure that could quickly deliver web content had a higher search ranking than those that were slower. This means that, despite conventional wisdom, it is back-end website performance and not front-end website performance that directly impacts a website's search engine ranking.
  • Our data shows there is no correlation between "page load time" (either document complete or fully rendered) and ranking on Google's search results page. This is true not only for generic searches (one or two keywords) but also for "long tail" searches (4 or 5 keywords) as well. We did not see websites with faster page load times ranking higher than websites with slower page load times in any consistent fashion. If Page Load Time is a factor in search engine rankings, it is being lost in the noise of other factors. We had hoped to see some correlation especially for generic one- or two-word queries. Our belief was that the high competition for generic searches would make smaller factors like page speed stand out more.
  • TTFB is affected by 3 factors: The network latency between a visitor and the server. How heavily loaded the web server is. How quickly the website's back end can generate the content.
  • Websites can lower network latency by utilizing Content Distribution Networks (CDNs). CDNs can quickly deliver content to all visitors, often regardless of geographic location, in a greatly accelerated manner.
  • Do these websites rank highly because they have better back-end infrastructure than other sites? Or do they need better back-end infrastructure to handle the load of ALREADY being ranked higher? While both are possible, our conclusion is that sites with faster back ends receive a higher rank, and not the other way around.
  • The back-end performance of a website directly impacts search engine ranking. The back end includes the web servers, their network connections, the use of CDNs, and the back-end application and database servers. Website owners should explore ways to improve their TTFB. This includes using CDNs, optimizing your application code, optimizing database queries, and ensuring you have fast and responsive web servers.
  • Fast websites have more visitors, who visit more pages, for longer period of times, who come back more often, and are more likely to purchase products or click ads. In short, faster websites make users happy, and happy users promote your website through linking and sharing. All of these things contribute to improving search engine rankings.
Pedro Gonçalves

Survey: Tablet Owners Prefer Browsers to Native Apps - 0 views

  • Among tablet owners, at least, reading on the mobile Web is preferable to using native apps, according to a recent survey from the Online Publishers Association. 
  • Forty-one percent of tablet-bound readers prefer reading on the Web, compared to the 30% who would rather launch a standalone app from a specific publisher. Aggregated news-reading apps like Flipboard and Zite rated surprisingly low on the list. 
  • Last month, Jason Pontin, editor of MIT Technology Review, wrote a widely read takedown of native apps, citing Apple's steep revenue share and the technical and design challenges associated with producing such apps.  "But the real problem with apps was more profound," Pontin wrote. "When people read news and features on electronic media, they expect stories to possess the linky-ness of the Web, but stories in apps didn’t really link."
  • ...4 more annotations...
  • Apple's infamous 30% subscription revenue cut prompted the Financial Times to abandon its iOS apps and instead focus on developing a cross-platform Web app written in HTML5. 
  • Evidently, the native-app approach is not working for readers, either - at least, not as well as the Web. FT has seen an increase in readership and paid subscriptions since going the HTML5 route, Grimshaw said. 
  • Native apps do offer potential advantages in terms of the reader's experience. They can be more immersive and lack some of the design limitations of the Web. Still, in far too many cases, apps created by publishers end up being little more than digital reproductions of the print product with a few bells and whistles tacked on. 
  • From the reader's standpoint, it makes sense that the Web would be a popular option for tablet reading. After all, there's much more content there, and it's intricately linked together. A digital magazine can offer a refreshing escape from the anarchy of the Web, but it's only a matter of time before readers find it necessary to return to a browser. 
Pedro Gonçalves

In 2014, The Mobile Web Will Die-And Other Mobile Predictions - ReadWrite - 0 views

  • In 2014, the mobile Web will die. That’s right, that bastardized version of the normal Web will crawl into a shallow grave and leave us all in peace. No more websites crippled with horrible “mobile.yourawfulwebsite.com” URLs. No more reading janky websites that display way too much fine print or omit crucial features when viewed on your smartphone or tablet. 
  • The mobile Web will die because the companies that make the engines it ran upon are killing their mobile browsers and replacing them with fully functional versions that run on any device. In 2014, these browsers will be updated to put the final nail in its coffin. In turn, developers will continue to build websites that can work across any screen size. Responsive design (what we do at ReadWrite to make the site look pretty everywhere) will continue to grow in 2014 as people realize that their old websites are losing them a lot of traffic from mobile devices.
  • Location-based consumer apps didn't let me down; as predicted, they remained stagnant this year. Foursquare and its kindred just are not hot anymore, even if Foursquare did just raise a funding round this week.
  • ...2 more annotations...
  • HTML5 Takes Over The Mobile Web
  • Combined with CSS and JavaScript, HTML5 is what the Web will be built on in the future. And it will just be the Web, mobile or otherwise.
Pedro Gonçalves

Snow Fail: Do Readers Really Prefer Parallax Web Design? | Co.Design | business + design - 0 views

  • The parallax style has excited web developers and inspired any number of hype lists. It's also triggered a backlash among critics who feel its bells-and-whistles approach detracts from actual content. Pitchfork creative director Michael Renaud recently told the Atlantic Wire he expects people to "tire" of the trend within a year or two.
  • the parallax site was only superior in one sense--fun. None of the other survey measures indicated a significant difference in user experience between the two sites. Parallax didn't even edge the standard site in questions about visual appeal (although participants did think it looked slightly more "professional"). Frederick also discovered one critical disadvantage of parallax: test participants who suffered from motion sickness found the style disorienting.
  • Sobering as this first careful study of parallax might be to web designers, Frederick still believes it's a fad with a future. He cautions developers to think more carefully about the context in which parallax is applied. Text-heavy sites that employ parallax scrolling seem more likely to disorient users, he says. Sites that emphasize visual elements--images, infographics, or data visualizations, in particular--are probably a better fit for the style.
Pedro Gonçalves

Standards and benchmarks - 0 views

  • The average top 1,000 web page is 1575 KB.
  • Page growth is a major reason why we keep finding, quarter after quarter, that pages are getting slower. And faster networks are not a cure-all for the challenges of page bloat.
  • According to Akamai’s most recent quarterly State of the Internet report, the global average connection speed among the top 50 internet-using countries is 3.3 Mbps — a 5.2% increase over the previous quarter. But when we’re seeing year-over-year page growth ranging from 45-50%, it’s easy to see that the gap is widening.
  • ...16 more annotations...
  • A whopping 804 KB per page is comprised of images. Three years ago, images comprised just 372 KB of a page’s total payload.
  • images are one of the single greatest impediments to front-end performance. All too often, they’re either in the wrong format or they’re uncompressed or they’re not optimized to load progressively — or all of the above.
  • Today, 38% of pages use Flash, compared to 52% in 2010. This is a good thing. Nothing against Flash, per se, but if Apple has no plans ever to support it, its obsolescence is inevitable in our increasingly mobile-first world.
  • use of custom fonts has exploded — from 1% in 2010 to 33% today.
  • But custom fonts have a dark side: they can incur a significant performance penalty.
  • These days, images on the web have to work hard. They need to be high-res enough to satisfy users with retina displays, and they also need to be small enough in size that they don’t blow your mobile data cap in one fell swoop. Responsive web design attempts to navigate this tricky terrain, with varying degrees of success.
  • Move scripts to the bottom of the page
  • Here at Strangeloop/Radware, we’ve found the opposite. Using WebPagetest, we’ve been testing the same 2,000 top Alexa-ranked ecommerce sites since 2010, and our data tells us that top ecommerce pages have gotten 22% slower in the past year.
  • This quick-and-dirty case study illustrates how network speed doesn’t directly correlate to load time. For example, download bandwidth increases 333% from DSL (1.5Mbps) to cable (5Mbps), yet the performance gain is only 12%.
  • Google published findings, based on Google Analytics data, which suggest that load times have gotten marginally faster for desktop users, and up to 30% faster for mobile users.
  • It’s better to move scripts from the top to as low in the page as possible. One reason is to enable progressive rendering, but another is to achieve greater download parallelization.
  • Make JavaScript and CSS external
  • If users on your site have multiple page views per session and many of your pages re-use the same scripts and stylesheets, you could potentially benefit from cached external files. Pages that have few (perhaps only one) page view per session may find that inlining JavaScript and CSS results in faster end-user response times.
  • Reduce DNS lookups
  • Minify JavaScript
  • In addition to minifying external scripts, you can also minify inlined script blocks. Even if you’re already gzipping your scripts, minifying them will still reduce the size by at least 5%.
Pedro Gonçalves

Tablet Mobile Web Traffic Now Eclipses Smartphone Traffic [Charts] - ReadWrite - 0 views

  • Adobe analyzed more than 1 billion visits for more than 1,000 websites and found that 8% of traffic came from tablets. That ranks ahead of the 7% of visits that came from smartphones. Of course, that leaves 85% or so percent of Web traffic still coming from desktop PCs and laptops. 
  • no matter how much we harp on the notion that the mobile Web is not just the future, but also the present, the vast majority of Web traffic still comes from the legacy that is the PC. 
Pedro Gonçalves

Web Developers Brace For the MacBook Pro's Retina Display - 0 views

  • The new laptop, which Apple unveiled last week, already has Web designers and developers trying to figure out how they're going to create sites and Web apps that look good on the new machine without leaving the rest of the Web's population behind.
  • One of the key advantages of these high-resolution displays is their crisp, highly readable rendering of text. That particular buck stops with the Web browsers, which are much more varied on the desktop than on mobile devices. Naturally, Safari supports retina-friendly text, but Chrome is still working on it, and other browsers will presumably follow.
  • For image-heavy sites, swapping out higher-resolution images can have a substantial impact on page load, which in turn affects user experience and even search engine rankings. 
  • ...2 more annotations...
  • To deal with this issue, Web developers can borrow from some of their tried-and-true methods. For years, websites have used browser detection to deliver different CSS stylesheets to different browsers. A similar approach is used to craft responsive designs - when sites load different layouts depending on the device being used to view it. Likewise, this sort of tactic could be used to handle graphics
  • That's exactly what they're doing at O3 World, an interactive agency based in Philadelphia. To account for different screen resolutions, they've begun creating multiple sets of graphics, which are delivered dynamically, depending on the user's screen resolution.
Pedro Gonçalves

Latency: The New Web Performance Bottleneck - igvita.com - 0 views

  • Upgrading your connection from 1Mbps to 2Mbps halves the PLT, but quickly thereafter we are into diminishing returns. In fact, upgrading from 5Mbps to 10Mbps results in a mere 5% improvement in page loading times!
  • For every 20ms improvement in latency, we have a linear improvement in page loading times.
  • Latency on the other hand affords no such "easy" wins. Yes, the equipment can be improved to shave off a few milliseconds, but if you want significant improvements, then the answer is simple: you need new, shorter cables to reduce the propagation delay.
  • ...6 more annotations...
  • In 2012, the average worldwide RTT to Google is still ~100ms, and ~50-60ms within the US.
  • Fiber-to-the-home services provided 17 milliseconds (ms) round-trip latency on average, while cable-based
  • That's 17-44ms of latency just to the closest measuring node within your ISP, before your packet hits any internet backbone.
  • depending on your network, quality of signal, and time of day, then just traversing your way to the internet backbone can take anywhere from 50 to 200ms+. From there, add backbone time and multiply by two: we are looking at 100-1000ms RTT range on mobile.
  • the only way to improve the situation is to move the bits closer: place your servers closers to your users, leverage CDN's, reuse connections where possible (TCP slow start), and of course, no bit is faster than no bit - send fewer bits.
  • "High speed" connectivity is not all about bandwidth, unlike what many of our ISPs would like to promote.
Pedro Gonçalves

25 years after inventing the web, Tim Berners-Lee invites users to help draft global "b... - 0 views

  • The principles behind Web We Want, which is coordinated by the World Wide Web Foundation, are as follows: Affordable access to a universally available communications platform The protection of personal user information and the right to communicate in private Freedom of expression online and offline Diverse, decentralized and open infrastructure Neutral networks that don’t discriminate against content or users
Pedro Gonçalves

How To Make Your Websites Faster On Mobile Devices | Smashing Mobile - 0 views

  • A recent study (PDF) found that more than 80% of people are disappointed with the experience of browsing Web on mobile devices and would use their smartphones more if the browsing experience improved.
  • A recent study (PDF) found that more than 80% of people are disappointed with the experience of browsing Web on mobile devices and would use their smartphones more if the browsing experience improved.
  • 64% of smartphone users expect websites to load in 4 seconds or less, while the average website takes more than twice that amount, at 9 seconds.
  • ...3 more annotations...
  • On a desktop, only 20% of the time it takes to display a Web page comes from downloading files. The rest of the time is spent processing HTTP requests and loading style sheets, script files and images. It takes even longer on a smartphone because its CPU, memory and cache size are much smaller than a desktop’s.
  • Having a fast website is all about making the hard decisions and getting rid of what’s not at the core of your experience. If it doesn’t add a lot of value, remove it.
  • Reduce DependenciesFewer files to download means fewer HTTP requests and faster loading times. Reduce Image DimensionsOn top of the extra download time, precious processing power and memory are used to resize high-resolution images. Reduce Client-Side ProcessingRethinking the use of JavaScript and keeping it to a minimum are best.
Pedro Gonçalves

New Defaults In Web Design - How Much Has The Web Really Changed? | Smashing Magazine - 0 views

  • Many mouseover interactions are completely dysfunctional on a touch device
  • Instead of buying a state of the art monitor, buying a cheap monitor and several low-end devices to test your work on might be a better investment.
  • Hiding content and showing it on mouseover was considered to be a decent design pattern
  • ...13 more annotations...
  • When you hover over a menu item, a submenu appears. But apart from hovering over an item, you can also simply click on it to follow the link. Now, what should happen when you tap on the item with a touch device? Should the submenus appear, or should the link activate? Or both? Or should something else happen? On iOS, something else happens. The first time you tap a link like that, the submenu appears; in other words, the hover event fires. You have to tap a second time to actually follow the link. This is confusing, and not many people will tap a second time. On Android, the submenu appears and the link is followed simultaneously. I don’t have to explain to you that this is confusing.
  • It’s very well possible to think of complex solutions11 whereby you define different interactions for different input devices. But the better solution, I think, is to make sure that the default interaction, the activate event, just works for everybody. If you really need to, you could choose to enhance this default experience for certain users.
  • The same principle that we follow for interactions — whereby we design the activate event first and enhance it later — applies to graphic design. We should start designing the things that we know everyone will see. That’s the content. No matter how big or small a screen is and no matter how minimal the feature set of a browser, it will be able to show letters.
  • rather than pollute the page with all kinds of links to get people out of there, we should really focus on that thing in the middle. Make sure it works. Make sure it looks good. Make sure it’s readable.
  • you start by designing the relationship between the different font sizes.
  • When the typography is done, you would start designing the layout for bigger screens; you can think of this as an enhancement for people with bigger screens. And after that, when the different layouts are done, you could add the paint. And by paint, I mean color, gradients, borders, etc.
  • When I say to start with typography, I don’t mean that you aren’t allowed to think about paint at the same time. Rather, I’m trying to find the things that all of these different devices, with all of their different screen sizes and all of their different features, have in common. It just seems logical to first design this shared core thoroughly. The strange thing is that this core is often overlooked: Web professionals tend to view their own creations with top-of-the-line devices with up-to-date browsers. They see only the enhancements. The shared core with the basic experience is often invisible.
  • All of the things we created first — the navigation, the widgets, the footer — they all helped the visitor to leave the page. But the visitor probably wanted to be there! That was weird.
  • To build a responsive website that works on all kinds of screens, designing for a small screen first is easiest. It forces you to focus on what’s really important: if it doesn’t fit in this small square, it is probably not terribly important. It forces you to think better about hierarchy, about the right order of components on the page.
  • Once you’re done with the content, you can start to ask yourself whether this content needs a header. Or a logo. Or subnavigation. Does it need navigation at all? And does it really need all of those widgets? The answer to that last question is “No.” I’ve never understood what those widgets are for. I have never seen a useful widget. I have never seen a widget that’s better than white space.
  • does the logo really need to be at the top16 of every page? It could very well go in the footer on many websites
  • the option to add extra luggage to a flight booking might be most effective right there in the overview of the flight, instead of in the middle of a list of links somewhere on the left of the page.
  • does the main navigation look more important than the main content? Most of the time it shouldn’t be, and I usually consider the navigation to be footer content.
Pedro Gonçalves

Mozilla's First Peak Of Firefox OS Smartphones - ReadWrite - 0 views

  • Firefox OS is of the Web, for the Web. There is no such thing as a “native” app to Firefox OS. If an object exists as a web page, it can easily be turned into an app for Firefox OS by essentially turning it into a shortcut for the browser-based operating system to access. Instead of having to develop specifically for mobile platforms like iOS, Android or Windows Phone, the Web is the platform for Firefox OS. 
  • If you are a developer, you can build an app for Firefox OS by making some small changes to your website. You can then test the app by downloading the Aurora Marketplace onto your Android or using the browser-based Firefox OS Simulator. 
Pedro Gonçalves

A Primer on Responsive Design | UX Magazine - 0 views

  • According to IDC, mobile web browsing will soon eclipse desktop browsing in the U.S. and worldwide. This consumption of mobile content isn’t just happening on the go; 93% of people are now using their mobile devices to browse the Web from their homes, according to a study from Google.
  • The main development methodology behind responsive design is the use of media query functionality in CSS3. Media queries target not only certain device types (e.g., Android vs. iPhone), but actually inspect the physical characteristics of the device that renders the page. For example, the code below “asks” the device if its max horizontal resolution is equal to 480px: <link rel="stylesheet" type="text/css", media="screen and (max-device-width: 480px)", href="http://uxmag.com/iphone.css" /> If it is 480px, the device will load iphone.css. If not, the link is ignored. You can also include media queries in CSS as part of an @media rule:
  • a responsive design approach does not involve putting all of your content in front of the reader. Responsive design is about putting the right content in users’ hands according to the context of their interaction.
Pedro Gonçalves

How Google's Redesigned Search Results Augur A More Beautiful Web | Co.Design | busines... - 0 views

  • For Google to eliminate underlines as well is simply the final nail in the coffin for this old web standard. But that step is necessary in an era when we navigate the web by other means than a mouse.
  • the pesky underlines still pop up if you mouse over them.)
Pedro Gonçalves

France's Web Users Say 'Non' to Social Media Ads - eMarketer - 0 views

  • Unwelcome news for marketers in France who aim to appeal to people on social networks: A majority of those consumers find such ads unpleasant, useless and poorly targeted.
  • Sixty-eight percent of web users polled said they found advertising on social sites “intolerable, “ and 59% said it was pointless because it did not reflect their interests or buying habits.
  • Moreover, ads on these sites seemed to be less effective than most other kinds of online advertising. Only 19% of web users polled by IFOP and Generix said they had ever bought a product or service as a result of seeing an ad on social media, compared to 60% who had made a purchase prompted by an email.
  • ...3 more annotations...
  • Three-quarters of respondents said they never bought anything on social sites. While 9% said they did so from time to time, just 1% said they made regular purchases on social networks.
  • only 16% of social network users sampled in June and July 2013 had become clients of a brand after connecting with it on a social network or seeing an ad on such a site—though 38% of web users active on social media said they took account of opinions or comments about brands before making a purchase.
  • The number of social network users in France this year will be 23.7 million, eMarketer estimates.
Pedro Gonçalves

How People Read on the Web: The Eyetracking Evidence | Nielsen Norman Group Report - 0 views

  • Gaze patterns users commonly exhibit and accommodating these behaviors F-pattern Layer Cake Pattern Bypassing Pattern Spotted Pattern Commitment Pattern Scanning vs. reading, why people do it, and how to drive user behavior with your design
  • Kick effect: People look at the last result on a SERP before leaving the page. (The tenth organic result, on a page of 10 results, is the lowest result looked at in 12% of cases versus 7% combined for the seventh, eighth, and ninth results. In 59% of cases people looked no farther than the third organic result.)
  • Other patterns such as skipping, backtracking, love at first sight, zigzag, re-acclimating, and bypassing
  • ...1 more annotation...
  • People look at lists with bullets more often than lists without bullets (70% vs. 55%, respectively).
Pedro Gonçalves

How Users Read on the Web - 0 views

  • 79 percent of our test users always scanned any new page they came across; only 16 percent read word-by-word. (Update: a newer study found that users read email newsletters even more abruptly than they read websites.)
  • Web pages have to employ scannable text, using highlighted keywords (hypertext links serve as one form of highlighting; typeface variations and color are others) meaningful sub-headings (not "clever" ones) bulleted lists one idea per paragraph (users will skip over any additional ideas if they are not caught by the first few words in the paragraph) the inverted pyramid style, starting with the conclusion half the word count (or less) than conventional writing
Pedro Gonçalves

ReadWrite - Facebook Mobile Use May Be Near Its Saturation Point In The United States - 0 views

  • social media use on mobile devices rose 63% between native apps and the mobile Web in the United States in 2012.
  • Between PCs and mobile devices, Americans spent 121 billion minutes on social media in July 2012, an increase of 37% (88 billion minutes). 
  • In the United States, 152 million people accessed Facebook from their PCs against 152.7 million through either native apps or the mobile Web.
  • ...1 more annotation...
  • Granted, there is likely some overlap accessing Facebook on both the mobile Web and native apps,
Pedro Gonçalves

Shullman Research Data Confirms Your Rich Friends Don't Really Want to See You in Perso... - 0 views

  • h. People with a household income of $250,000 and up are more likely to use the Web to stay in touch with friends and family (96 percent) than traditional ways (81 percent), according to the Shullman Luxury and Affluence Monthly Pulse. Email is the most popular Web-based method (favored by 78 percent), followed by texting (65 percent) and Facebook (55 percent), although it’s notable that among those under 35, Facebook is preferred by 69 percent. Business communication is also moving online; 89 percent prefer Web-based options versus 75 percent who use traditional ways, although among the under-35 age group, that figure falls to below 50 perce
1 - 20 of 288 Next › Last »
Showing 20 items per page