Articles

Asset management and website performance optimization are two of those unavoidable headaches faced by every website owner.

A digital asset management (DAM) platform can provide centralized asset repositories with intuitive dashboards to help you manage assets. On the other hand, an image CDN can help you get rid of that messy responsive syntax and provide dynamic asset optimization with huge performance boosts.

The problem is that website performance has become such a competitive factor that DAMs with other priorities tend to fall short. On the other hand, specialized image CDNs don’t solve the problems associated with image management, particularly within organizations.

With that in mind, I propose solving these problems for good by putting together image management and optimization stack using ImageEngine and Cloudinary. Instead of being a comparison between these two tools, this article describes the benefits of using them to complement each other.

Features and Asset Management Capabilities

As a DAM, Cloudinary provides you with a visual interface to store, manage, and edit your image and video assets. In that way, it’s not much different from any other professional image managing software such as Adobe Bridge, except that it’s an online, browser-based service.

Using the Media Library, you can upload, delete, and organize images in folders, for example. The visual image editor allows you to make advanced transformations and image touch-ups and see the results instantaneously using tools like sliders, dropdowns, etc. You can even chain transformations together for multi-layered effects.

Cloudinary also allows you to manipulate images and videos this way using their URL-based API.

Cloudinary has additional auxiliary features that make asset management easier (especially in organizations), such as backups, role-based multi-user admin, and feature extensions via third-party integrations and add-ons.

This is something most image CDNs don’t provide. Instead, they allow you to access and transform images using URL manipulation. Transformations are usually made using string-based parameters or directives. A serverless, headless DAM, if you will.

However, the advantage of using a dedicated image CDN like ImageEngine, is that it can usually provide enhanced asset optimization. ImageEngine, for example, is an intelligent image CDN that uses WURFL device detection to finely read the context an image is accessed from (device model, PPI, OS, browser, resolution, etc.) and then chooses the optimal image for that configuration.

This frees up website owners from having to do any additional optimization. This business logic is also built-in to all of their global PoP servers, and ImageEngine specifically delivers cache-hit ratios close to 100%. The following performance section will illustrate the difference this can make in practice.

Check out the key differences between ImageEngine and Cloudinary. And, for a deeper insight, see the comparison with other similar CDNs, like imgix and Cloudflare

Performance

Just to cover our bases and prove that this is an effective asset management and optimization stack, I’m also going to affirm it using a Lighthouse performance audit. Here is a quick summary of the results:

For this test, I built a web page with a tonne of images with overly large file sizes. In this first Lighthouse audit, I didn’t apply any optimization to the images. Here’s the result:

As you can see, we had some major problems when it came to the loading time of our assets. Overall, the page took more than 10 seconds to load. One of Google’s crucial user-centric performance metrics, LCP, scored a miserable 7.5s. Lighthouse suggested that some of the main problems encountered were the asset file size, inefficient cache policies, using non-optimal image formats, and improperly sized images.

Both Cloudinary and ImageEngine are supposed to address all of these factors with their auto image optimization. In the next audit, I used the same page and content but served my images via Cloudinary:

As you can see, there is improvement in most factors. FCP is now in the green, and both the Speed index and LCP times have almost halved. Even TTI and CLS improved slightly. That being said, it’s still nowhere near optimal, and we’re still falling short of the all-important 3-second loading time ceiling.

So, finally, let’s do another Lighthouse audit – this time using ImageEngine on top of Cloudinary. Here are the results:

With ImageEngine, I finally scored in the green with 95. All the metrics that have to do with the sheer speed at which image content loads improved. The Speed Index and LCP, which is the most important, improved dramatically. CLS scored worse, but this typically varies from test to test.

You can find another and more extensive breakdown of the performance and pricing comparison here.

Transformations, Bandwidth Utilization, and Cost

Cloudinary’s pricing plans work on a credit-based system. Starting with the free account, you get 25 credits/month. Each credit can be used for 1,000 transformations, 1 GB of storage, or 1 GB of net viewing bandwidth. The other two packages cost $99 for 225 credits and $249 for 600 credits, respectively.

You should plan to generate a minimum of 5 transformations per image. In effect, that limits you to around 200 images with the free plan, excluding whatever manual transformations you make.

ImageEngine’s Basic plan costs $49 and provides you with 100 GB of Smart Bytes. Smart Bytes are based on optimized image content and translate to roughly 400-500 GB of raw images.

So, with Cloudinary, you have to compromise between bandwidth and storage usage as well as the number of transformations you can make. Transformations for Cloudinary are counted as they are dynamically generated on-demand.

However, if you use ImageEngine for optimization, you can switch off Cloudinary’s auto-optimization. When a new image variant is needed, it will be generated and delivered via ImageEngine. Considering variant count isn’t limited by ImageEngine, this will drastically cut down on the number of credits you’ll need to spend on transformations.

Effectively, that means you could use the bulk of your Cloudinary credits purely for storage and specific transformations. For example, advanced cropping, applying effects, or color adjustments. These are, after all, the main functions of a DAM.

With this setup, ImageEngine’s Basic plan and Cloudinary’s free plan should be adequate for most websites, saving around $50 a month.

How to Implement Cloudinary with ImageEngine

Signing up for Both Services

As it will house all of your image assets, the logical place to start would be to sign up with Cloudinary.

Create a (free) account, and make sure to take note of your “cloud name” during the setup wizard. This will be the name of your designated storage location on the Cloudinary platform and is usually a garbled string like di2zgnxh0 by default. However, you can change this to something more meaningful.

Once you’ve signed up, you can start uploading your image assets and creating different versions/transformations of them. Setting up Cloudinary integration on a CMS, like WordPress, is usually straightforward. Just indicate the CMS you’ll be using, copy the API key, install the plugin, and activate it.

Next, sign up for a free trial with ImageEngine. There will also be a short setup wizard during which you will:

  1. Provide ImageEngine with the website where your images will be delivered.
  2. Supply your image origin (in this case, your Cloudinary web folder). For now, you can only add the Cloudinary, e.g., res.cloudinary.com.
  3. Get your ImageEngine image-serving domain, e.g., {randomstring}.cdn.imgeng.in

When in your ImageEngine dashboard, you’ll see this domain listed under “Engines” as well as an entry for Cloudinary under “Origins.” Edit the latter and under “Advanced,” add your Cloudinary folder to the “PATH” field.

That’s it, you should now be able to store and manage images via Cloudinary and serve them via the ImageEngine CDN.

Dynamically Loading Specific Image Variants

Let’s take a look at a use case for loading different transformations of individual images on your site. This example will showcase how you can use Cloudinary’s advanced image editing tools to transform images while still reaping the optimization rewards of using ImageEngine as your image CDN.

A popular practice today is to use rounded images for team, client, or profile portraits. Using Cloudinary, you can load this transformation using the following URL:

https://res.cloudinary.com/myimages/image/upload/w_400,h_400,c_crop,g_face,r_max/w_200/profile.jpg

This will resize the image to 400 by 400px, focus on the face, and apply the maximum amount of radial cropping around it – to a width of 200px.

The same image can then be accessed via your ImageEngine delivery engine simply by swapping out the domain:

https://images.myimageengine.com.imgeng.in/image/upload/w_400,h_400,c_crop,g_face,r_max/w_200/profile.jpg

NOTE: I added my Cloudinary folder designation (“myimages”) as the path to my image origin. With that config, I don’t need to include it every time I use the image URL.

For example, you can set up the origin like this:

And, then under advanced:

If I specifically wanted to load the profile picture in WebP format (for transparency support, for example), I could add the ImageEngine directive f_webp:

https://images.myimageengine.com.imgeng.in/image/upload/w_400,h_400,c_crop,g_face,r_max/w_200/?imgeng=/f_webp/profile.jpg

ImageEngine and Cloudinary – The Wrap Up

Both ImageEngine and Cloudinary are superb platforms that can make managing image and video assets easier and improve your website maintenance. However, both services have their specialty in which they outperform each other.

For ImageEngine, it’s delivering blisteringly fast image loading times in next-gen formats and with a minimal loss of visual quality.

For Cloudinary, it’s providing a visual interface to organize, store, and edit your image and video assets.

As a further incentive, letting each of these services handle what they’re best at can lead to lowering your long-term operating costs.

 

[– This is a sponsored post on behalf of ImageEngine –]

Source

The post Start Using a Smart DAM and Image Optimization Stack first appeared on Webdesigner Depot.


Source de l’article sur Webdesignerdepot

We all get excited about new projects; we’re daydreaming about possibilities from the first contact with a potential client. Most professionals have an established onboarding process, with contracts to sign and business assets to acquire; if you’re a coder, you probably set up a fresh new repository; if you’re a designer, you create a new project folder. All of us start imagining how the case study will look in our portfolio.

But few, if any, plan for the end of a project. Offboarding clients simply isn’t a thing. We build their site, and then one day, we don’t.

It may be that the client moves on; hopefully, you’ve done a good enough job that they can’t resist bringing you on board for their next startup. All too often, projects languish in some half-life, with occasional security patches that net you a whole $5 in service charges; is that why you got into web design? Probably not. There is the desirable option of upselling; if your client’s business grows due to your work, then more work should grow it some more.

If you’re great at startups, you’re probably not great at maintaining sites in the long term. If you’re great at maintaining sites, you’re probably not great at growing them.

For every cycle of a project’s life, there are different kinds of professionals who suit it best. And conversely, different cycles of a project suit you and your skillset better than others.

We all know that a bad client — demanding, rude, late at paying — should be fired. But what about a good client — a client who pays quickly, is friendly, professional, accommodating? Would you fire a good client if you’d outgrown the work?

Source

The post Poll: Should You Fire Good Clients? first appeared on Webdesigner Depot.


Source de l’article sur Webdesignerdepot

When I use map apps such as Google Maps, I often use Street View to display more detailed views of a street or inside of a building.  Although Google Street View is fantastic, there are many use cases where I want to control the development pipeline and assets without having to upload images to Street View. 

To control and optimize your business workflow, you can use open-source Marzipano to build virtual tours yourself and host the tours on your own web site.  This tutorial explains how to build the tour with open source software and host it for free on GitHub Pages. The technology and techniques can scale to large cloud businesses and are in production at commercial sites.   This tutorial focuses on a minimal simplified site to get you started with the basic concepts in minutes.

Source de l’article sur DZONE

The world of search engine optimization was born with all sorts of different hacks and shortcuts that many people use in an effort to grow their business.

Knowing effective SEO tricks would be incredibly profitable, but unfortunately it’s not that easy

This becomes evident as soon as you do a Google search about anything SEO-related, only to find pages and more pages replete with blog posts and videos disclosing all the tips and tricks you “need to know” in order to achieve the best SEO results, in the fastest way possible.

Knowing effective SEO tricks would be incredibly profitable, but unfortunately it’s not that easy.

In its essence, SEO isn’t about hacks, shortcuts, and hidden optimizations, but rather about resource allocation. Keep reading to learn why!

Be Careful About Over-Reliance on Hacks

Before we start talking about resources, it’s important to understand why the quick and easy SEO hacks we’ve all read about online aren’t as reliable as they might seem.

The reality is that yes, there are some traditional hacks and optimization tactics that many people swear by. However, SEO has become way too competitive for these hacks to still work.

Think about it: anyone can learn about these hacks and shortcuts in a matter of seconds, which means that anyone can use them, which means that they’re not going to help your website stand out. By way of example, when thinking about keyword usage, many websites simply decide to put them everywhere on their website, without actually planning and strategizing. Perhaps years ago, doing so would lead to excellent results, but that’s not the case anymore.

What I want to go over, and what I mean with this article, is that when developing your SEO plan, you should think less about hacks, and try to focus on strategy and resources instead.

As tempting as they might be, most SEO hacks won’t really go that far.

What does go far are those strategies and resource allocation decisions, which you can master as long as you know three things:

  • Who your competitors are;
  • What you have;
  • and What strengths you can double down on.

Base Your SEO Strategies on Your Business’s Resources

So, SEO is about resource allocation – we know that now…but what exactly does that mean?

Well, this logic is based on something you might have heard of before, and that is the three pillars of SEO.

As a refresher, everything in SEO revolves around three pillars:

  • Link building and referring domains;
  • Content development and content marketing;
  • Technical SEO.

Many businesses have a limited digital marketing budget and, as if that wasn’t enough, their SEO budget tends to be even more restricted.

This means that we can’t try every hack out there or do every campaign we can come up with, hoping it will lead to positive results. On the contrary, it means we need to be methodical and understand which strategies have the most potential and are actually worth exploring.

In summary, there’s one big challenge that every SEO team and company experiences, and that is the limitation of resources versus possible operations, and that leads us to a question: what mix of SEO pillars will give us a good shot at ranking high and surpassing our competitors?

Develop Your SEO Strategies Based on Your Inherent Strengths

The mistake that a lot of business owners make after reading SEO articles or hearing about amazing case studies is that they try and copy the strategies they learned about, from beginning to end.

However, contextually, each case study or article could refer to a strategy that was specifically optimized for a different type of business.

So, although copying what other successful businesses can work in certain situations when speaking about SEO, it’s best to borrow ideas and use the ones that fit your inherent strengths.

Based on the pillars of SEO that we discussed earlier, there are three strong points that a company can have:

If You Have a Strong Network…

Some businesses don’t have the resources to create an in-house content development team or outsource writing services.

However, they have another strong suit, which lies in their ability to go out into their community, speak, and be heard. They can do this because they have built a strong network over the years and, in cases like this, what we often do is use a backlinking approach.

When working with businesses that have a strong community presence, go out and double down on their network. Pitch their relevant contacts for guest speakership and guest posts, building thought leadership, while also driving links to their website.

If You’re Not That Popular But Are Good With Words…

Right now, some of you might be thinking: “Yeah, well, that’s easy when you’ve built the exposure, but not all of us are lucky enough to be well-known”.

Listen, I get it, we’ve all been in that position.

For clients and businesses that feel like they don’t have the brand equity or exposure to develop a strong backlinking strategy, opt for another route, and invest much more on content (and/or technical SEO, see below).

If the client has a team who’s ready to put its head down and get to work, then focus on producing a lot of content for their website.

Ultimately, the goal is to build a content library that is thorough and expansive, and that provides the client with more opportunities for keyword rankings, while also reinforcing the relevance of their website for those specific SEO keywords.

If Technical Knowledge is Your Forte…

You may not like (or have time) to write and you may not have a strong community presence, but if you have advanced technical skills and the ability to create a strong website quickly, then there’s another approach you can take.

This leads us into the third pillar of SEO: technical SEO.

This solution is indicated for technical teams that can create large websites, databases and user experiences in no time, and it is typically adopted by tech startups that are trying to create an app that provides user value.

First and foremost, winning at technical SEO requires strong technical skills that will allow you to build the web assets that you need, but that’s not all. It also requires you to understand how you can double down on these skills and manage large websites in the rather complex Google ecosystem.

So you need, for example, to know how you can get Google to notice and properly index the new pages you create on your website, even if you already have 100,000 pre-existing pages.

Or to ensure that each of your new pages is properly optimized for the best keywords.

Needless to say, using technical SEO does become a complex operation. However, when done right, it can lead your SEO to grow by sheer size, with the hopes that certain relevant keywords will start to rank for your business naturally.

Conclusion: Your Strategy Will Probably Be a Combination of the Three Pillars

When it comes to SEO, honing in on your strengths and accepting the fact that you can’t do everything is definitely the way to go.

When you’re running an SEO campaign, you should always focus on what you’re good at, know your resources, and augment what you already master – and that will put you in the right direction.

By focusing your resources on any of the pillars of SEO (or even a mix of them), you substantially increase your chances of achieving long-term success, which will not happen if you go for hacks and shortcuts instead.

A long-term, highly-organized, resource-allocated SEO strategy won’t only guarantee continuous success, but it can ultimately become self-sustaining, meaning that it will allow you to keep growing and growing, becoming an organic part of your marketing plan.

I’ve seen a lot of people try SEO hacks for two weeks, only to realize that they didn’t work and that their efforts had been in vain. 

It’s unfortunate because by doing so, you’re turning your back on a marketing channel that is very valuable to a lot of people, and these hacks trick people into thinking it’ll be overnight.

So remember, resource allocation over hacks and shortcuts!

Source


Source de l’article sur Webdesignerdepot

Google resembles an iceberg: there’s the part above the water we can see and use everyday; there’s also the part beneath the water, that we don’t see and know little about.

While many of us are concerned about the aspects of Google we don’t see — the parts that threaten our privacy, or monopolize the web — there’s no denying that Google offers some amazing products and tools, many of them free, all from the convenience of a single login.

Today we’re going to take a look at 12 tools from Google that really do bring something positive to the table.

1. Polymer

Polymer is an open-source JavaScript library from Google for building web applications using Web Components. The platform comes with a ton of libraries and tools to help designers and developers unlock the web’s potential by taking advantage of features like HTTP/2, Web Components, and Service Workers. 

The main feature of Polymer is Web Components. With Web Components, you can share custom elements to any site, work seamlessly with any browser’s built-in elements, and effectively use frameworks of all kinds. Products like LitElement (a simple base class for creating fast, lightweight web components) and PWA Starter Kit make Polymer easy to use. If you like, you can build your app entirely out of Web Components.

2. Lighthouse

Google Lighthouse is an open-source, automated tool for improving the quality of web pages. The software allows you to audit web pages for performance, SEO, accessibility, and more. You can run Lighthouse using ChromeDevTools, directly from the command line, or as a Node module. 

To use Lighthouse in Google Chrome, just go to the URL you want to audit (you can audit any URL on the web), open ChromeDevTools, and click the Audits tab. After you have run the audit, Lighthouse will give you an in-depth report on the web page. 

With these reports, you will see which parts of your web page you need to optimize. Each report has a reference doc that explains why that audit is important and also shows you the steps you can take to fix it. 

You can also use Lighthouse CL to prevent regression on your sites. Using Lighthouse Viewer, you can view and share reports online. You can also share reports as JSON or GitHub Gists. 

Lighthouse also comes with a feature called Stack Packs that allows Lighthouse to detect what platform a site is built on. It also displays specific stack-based recommendations.

3. Google Analytics

Google Analytics is the gold standard of analytics services. Google analytics can be installed on your site for free with a small amount of JavaScript and allows you to see all kinds of details about your site visitors, like what browser they’re using, and where they’re from.

By using Google Analytics you can make decisions about your site based on science, and therefore be somewhat confident that the decisions you make will result in the outcome you are expecting.

4. Flutter

Flutter is Google’s UI toolkit for building natively compiled applications for mobile, web, and desktop from a single codebase. The toolkit is open source and free to use. The best part of Flutter is that it works with existing code. 

The toolkit has a layered architecture that allows for full customization, which results in fast rendering and flexible designs. It also comes with fully-customizable widgets that allow you to build native interfaces in minutes. With these widgets, you will be able to add platform features such as scrolling, navigation, icons, and fonts to provide a full native performance on both iOS and Android.

Flutter also has a feature called hot reload that allows you to easily build UIs, add new features, and fix bugs faster. You can also compile Flutter code to native ARM machine code using Dart native compilers. 

5. Google API Explorer

Google has a huge library of APIs that are available to developers but finding these APIs can be difficult. Google API Explorer makes it easy for developers to locate any API. On the Google API Explorer web page, you will see a complete list of the entire API library. You can easily scroll through the list or use the search box to filter through the API list. 

The best part of Google API Explorer is that each link to a reference page comes with more details on how to use the API. API Explorer is an excellent way to try out methods in the Monitoring API without having to write any code.

6. Puppeteer

Puppeteer is a project from the Google Chrome team. The platform enables web developers to control a Chrome (or any other Chrome DevTools Protocol based browser) and execute common actions, much like in a real browser. Puppeteer is also a Node library and it provides a high-level API for working with headless Chrome. It is also a useful tool for scraping, testing, and automating web pages. 

Here are some things you can do with Puppeteer: generate screenshots and PDFs of pages, UI testing, test Chrome Extensions, automate form submission, generate pre-rendered content, and crawl Single-Page Applications. 

7. Codelabs

Google Developer Codelabs is a handy tool for beginner developers and even advanced developers who want to improve their knowledge. Codelabs provide a guided, tutorial, hands-on coding experience. Codelabs’ site is broken down into several tutorial sessions on different topics. 

With the tutorials on Codelabs, you can learn how to build applications from scratch. Some of the tutorial categories include Augmented reality, TensorFlow, Analytics, Virtual Analytics, G Suite, Search, Google Compute Engine, and Google APIs on iOS. 

8. Color Tool

Color Tool makes it easy for web designers to create, share, and apply colors to their UI. It also measures the accessibility level for any color combination before exporting to the palette. The tool comes with 6 user interfaces and offers over 250 colors to choose from. 

The tool is also very easy to use. All you need to do is pick a color and apply it to the primary color scheme; switch to the secondary color scheme, and pick another color. You can also switch to Custom to pick your own colors. After you have selected all your colors, use the Accessibility feature to check if all is good before exporting it to your palette. 

9. Workbox

Workbox is a set of JavaScript libraries and Node modules. The JavaScript libraries make it easy to add offline support to web apps. The Node modules make it easy to cache assets and offer other features to help users build Progressive Web Apps. Some of these features include pre-caching, runtime caching, request routing, background sync, debugging, and greater flexibility than sw-precache and sw-toolbox. 

With Workbox, you can add a quick rule that enables you to cache Google fonts, images, JavaScript, and CSS files. Caching these files will make your web page to run faster and also consume less storage. You can also pre-cache your files in your web app using their CLI, Node module, or webpack plugin. 

10. PageSpeed Insights

PageSpeed Insights is a handy tool from Google Developers that analyzes the content of a web page, then generates suggestions on how to make the page faster. It gives reports on the performance of a web page on both desktop and mobile devices. At the top of the report, PageSpeed Insights provides a score that summarizes the page’s performance. 

11. AMP on Google

AMP pages load faster and also look better than standard HTML pages on mobile devices. AMP on Google allows you to enhance your AMP pages across Google. It is a web component framework that allows you to create user-first websites, ads, emails, and stories. One benefit of AMP is that it allows your web pages to load almost instantly across all devices and platforms hence improving the user’s experience. 

12. Window Resizer

When creating websites, it is important that developers test them for responsive design – this is where Window Resizer comes in. Window Resizer is a Chrome extension that resizes the browser window so that you can test your responsive design on different screen resolutions. The common screen sizes offered are desktop, laptop, and mobile, but you can also add custom screen sizes. 

 

Featured image via Unsplash.

Source


Source de l’article sur Webdesignerdepot