This document discusses HTTP and HTTPS protocols. It provides information on web servers, HTTP requests and responses, status codes, headers, methods, and SSL/TLS encryption. The key points are:
- HTTP is an application layer protocol for distributed, collaborative hypermedia information systems. It uses a request-response protocol to transfer data between clients and servers.
- HTTP requests consist of a start line with method, URI and version, followed by headers and an optional message body. Common methods are GET, POST, PUT, DELETE.
- HTTP responses contain a start line with status code and reason, followed by headers and an optional message body. Status codes indicate success, redirection, client or server errors.
1) WebSockets allow for bidirectional communication between a client and server that overcomes limitations of HTTP such as polling. It uses a single TCP connection for sending messages back and forth.
2) The WebSocket handshake establishes a connection via HTTP that is then switched to the WebSocket protocol. Messages can then be sent simultaneously in both directions.
3) Compared to polling, WebSockets have much lower overhead since it uses a single connection rather than multiple HTTP requests, resulting in significantly lower bandwidth usage even with many connected clients.
Web performance across the HTTP to HTTPS transitionseanwalbran
The document discusses the challenges of transitioning a website from HTTP to HTTPS. It notes that performance during the transition is crucial as HTTPS can be slow by default due to additional network latency from encryption overhead and browser caching issues. It provides tips for prefetching content, using content delivery networks effectively, minimizing new socket creation, and addressing browser-specific caching quirks to improve performance.
HTTP (Hypertext Transfer Protocol) is an application-level protocol used globally for communication on the World Wide Web. It uses a request-response messaging system, whereby a client sends an HTTP request to a server, which sends back an HTTP response. The most common HTTP methods are GET, POST, HEAD, PUT, DELETE, TRACE, and OPTIONS. GET retrieves information from the server, POST submits data to be processed, and HEAD requests headers only. PUT uploads files, DELETE removes files, TRACE echoes requests, and OPTIONS lists supported methods.
WebSocket is a protocol that provides bidirectional communication over a single TCP connection. It uses an HTTP handshake to establish a connection and then transmits messages as frames that can contain text or binary data. The frames include a header with metadata like opcode and payload length. WebSocket aims to provide a standard for browser-based applications that require real-time data updates from a server.
The document discusses the evolution of the web platform and browser security. It covers the basic technologies that underlie the web like HTML, CSS, JavaScript, and HTTP. It describes how these technologies work together to deliver content to users and allow for client-side interactivity. Key elements covered include HTML elements and tags, how CSS and JavaScript are used in web pages, JSON for data formatting, URIs for resource identification, the HTTP request/response protocol, and common HTTP methods and headers.
Maximizing SPDY and SSL Performance (June 2014)Zoompf
Presented at the Atlanta Web Performance Meetup Group on June 2014, Billy Hoffman from Zoompf shows how to improve the performance of your website using SPDY and SSL and discusses SSL issues such as Heartbleed and CRIME
1. The document discusses a meetup about WebSocket and SPDY protocols on July 5th, 2012 presented by Kensaku Komatsu.
2. The presentation covered introductions to WebSocket and SPDY, how they address issues with HTTP such as slow loading of multiple resources, and compared their communication models and transport protocols.
3. The main topics were introductions to WebSocket and SPDY, and a deeper dive into the WebSocket protocol including its handshake process, data framing, ping/pong functionality, and additional aspects like subprotocols and extensions.
JS Applications need to exchange data with Backend APIs running on domains other than your own – understanding the same origin policy CSP, CORS and postMessage.
Talk held on Grill.js conference in Wroclaw, Poland on 2018-08-18.
A talk about TCP, UDP, IP, DNS, ISP, GET, URI, URN, URL, SSL, TLS, TTFB, HTTP/2, HTML and DOM, or, in translation, a talk about the internet, how requests travel through the network and how browsers handle the response.
This has been originally presented during BrightonSEO - Summer 2021.
This document provides an overview of HTML5 WebSocket technology. It discusses limitations of traditional HTTP and how WebSocket enables full-duplex communication by reducing overhead and latency compared to alternative techniques like polling. The WebSocket API and protocol are introduced, along with browser support and server library options. Key benefits of WebSocket include unlimited connections per server, very small overhead, and true real-time bidirectional communication across the web.
WebSockets allow for bidirectional communication between a client and server over a single TCP connection. They improve on older "Comet" techniques which used polling and long-polling to simulate real-time updates. With WebSockets, the client can open a WebSocket connection to the server which sends messages at any time without needing an explicit request. This enables real-time applications with constantly updating information. The document outlines the WebSocket protocol, provides examples of the API in browsers, and discusses frameworks for building WebSocket applications.
This document discusses token binding as a way to more securely bind security tokens like cookies to client devices. It summarizes the core token binding specifications from the IETF, how token binding can be applied to single sign-on with OpenID Connect and OAuth, and the current landscape of implementations. Token binding allows binding of tokens to a client-generated public-private key pair to prove possession of the private key over TLS. This can help mitigate risks from cross-site scripting and other attacks. Specifications are being developed for token binding in areas like OpenID Connect and OAuth, and implementations exist in browsers, servers, and libraries.
HTTP is an application layer protocol for distributed, collaborative hypermedia information systems. It uses a request/response model where clients send requests to a server, which responds with status codes and messages. HTTP works over TCP and uses ports 80 and 443. HTTPS is HTTP secured with TLS/SSL for encryption and authentication to prevent eavesdropping and man-in-the-middle attacks. Key aspects of HTTP include methods, headers, cookies, caching, and TLS handshake.
Peter Lubbers from Kaazing gave a presentation on HTML5 WebSocket and communication technologies to the San Francisco Java User Group. He discussed the limitations of traditional HTTP for real-time applications and how technologies like polling and long polling add complexity. He then introduced HTML5 WebSocket as a new standard that enables true full-duplex communication with low latency. Finally, he briefly covered other HTML5 communication features like Server-Sent Events, XMLHttpRequest Level 2, and Cross Document Messaging.
On the one hand, browser extensions, e.g., for Chrome, are very
useful, as they extend web browsers with additional functionality
(e.g., blocking ads). On the other hand, they are the most
dangerous code that runs in your browsers: extension can read and
modify both the content displayed in the browser. As they also can
communicate with any web-site or web-service, they can report both
data and metadata to external parties.
The current security model for browser extensions seems to be
inadequate for expressing the security or privacy needs of browser
users. Consequently, browser extensions are a "juice target" for
attackers targeting web users.
We present results of analysing over 2500 browser extensions on how
they use the current security model and discuss examples of extensions
that are potentially of high risk. Based on the results of our
analysis of real world browser extensions as well as our own threat
model, we discuss the limitations of the current security model form a
user perspective.
need of browser users.
This document discusses techniques for optimizing web performance on mobile. It begins by noting common metrics for performance goals like first meaningful paint and interactive. It then discusses challenges of mobile like slower cellular networks and how users leave pages that take over 3 seconds to load. The rest of the document provides tips in several areas: optimizing the first load, improving data transfer, better resource loading, optimizing images, and enhancing the user experience. Specific techniques mentioned include avoiding extra roundtrips, using modern cache controls, preloading resources, lazy loading images, leveraging new APIs, and getting reports from the browser. The overall message is that web performance should be a top priority.
Cannibal Content - Stop Your Website From Eating Itself | Brighton SEO 2015Chris Green
How to stop cannibal content giving you a hard time - the slides from Brighton SEO, September 2015.
1) Be aware of the cannibals
2) Gain the tools to fight cannibalisation
3) To spur you on to do something about it
http://www.strategiqmarketing.co.uk/seo/brightonseo-slides-cannibal-content/
http://www.twitter.com/chrisgreen87
This document provides tips for optimizing websites for mobile through on-page SEO techniques. It recommends making sites responsive, reducing file sizes like images, using structured data to enhance listings, and optimizing page speed. Specific techniques include using frameworks like Bootstrap, optimizing images with srcset, adding schema.org markup, and using PageSpeed Insights to identify optimizations while accepting its limitations. The overall message is to structure, optimize and speed up content for all devices.
HTTPS: What, Why and How (SmashingConf Freiburg, Sep 2015)Guy Podjarny
When users use our sites, they put their faith in us. They trust we will keep their information from reaching others, believe we provided the information they see, and allow us to run (web) code on their devices. Using HTTPS to secure our conversations is a key part of maintaining this trust.
If that’s not motivation enough, the web’s giants are actively promoting HTTPS, requiring it for features such as HTTP2 & ServiceWorker, using it for search engine ranking and more. To make the most of the web, you need to use HTTPS.
This deck reviews what HTTPS is, discusses why you should prioritize using it, and cover some of the easiest (and most cost effective) steps to get started using HTTPS
An overview of the challenges of large site SEO architecture and a case for a new pattern of developing the web - "Destination Oriented Architecture". Followed by the proposed measurement framework of "Destination to Crap Ratios" and a set of technical examples of applying these ideas.
This presentation is a basic insight into the Application Layer Protocols i.e. Http & Https. I was asked to do this as a part of an interview round in one of the networking company.
-Kudos
Harshad Taware
Bangalore ,India
BrightonSEO Paul Madden Kerboo - Managing relationships for linksPaul Madden
This document provides guidance on systematically managing relationships and links. It emphasizes that link building and outreach are about relationships, not just content or promotions. It recommends focusing on understanding people's motivations by finding emotional triggers. Connections should be fostered over time by becoming a helpful resource rather than just promoting content. The goal is to build long-term influencer networks that provide ongoing benefits.
Merging Your Business Into The 24 Hour News CyclePippa Moyle
Content may be king, but in this noisy digital world, posts can easily be dethroned. Grabbing and holding the attention of your reader is difficult when new information is one easy click away. Those who succeed in this challenge are journalists. In this talk, Pippa discusses how and why applying journalistic techniques to create concise, authentic and newsworthy content will help your business to stand out above the noise.
*This talk was first given at the Brighton SEO.
(All photos were taken by me - unless stated otherwise)
BrightonSEO Keynote: The Good, The Bad and The Ugly of International SEOOban International
Internationalisation: The Good, the Bad and the Ugly. Emily Mace, Head of SEO at Oban Digital, discusses three examples of brands which have expanded into new markets with varying degrees of success and practical illustrations of why they have failed and succeeded.
Dominating Organic Search using Cutting-Edge SEO Analysis - BrigtonSEO 2015Razvan Gavrilas
Entering a New Market or Trying to Improve Your Rankings is always a struggle.
Applying the techniques shown in this presentation will provide you with information that could change the way you run your online marketing strategy and even your entire business.
The presented methodology allows you to benchmark entire markets. This will provide you with business intelligence that will allow your business to grow faster and be strategically organized.
A physical address is a strategic asset in local searchMiShop.local Ltd
Different ways to leverage a physical address in local search.
Brands with a physical high-street presence have a strategic advantage in local search over brands that do not.
This presentation talks about different types of local presence scenarios and how to leverage them in search, including: concession brands, service area businesses and conventional retail premises.
SERPs to Markup: How to Increase Your Earned TrafficKaizen
As Search Engines & Social Networks continually shift towards using personalised data and reduce organic results, this presentation runs through the latest structured data trends and how you can use markup, plugins and code that you can use to increase your earnt traffic & CTR from Organic & Social Channels.
This presentation explains how to create strategies using decisive, action-based and commercially focused language which will get clients as bought into the work we’re going to do as we are.
SERPs: From keyword to click. BrightonSEO (18th September 2015)Similarweb
This deck analyses user behaviour in terms of search and was originally presented at BightonSEO on Friday, 18th September 2015, written and presented by Gerald Murphy.
Topics included and discussed:
Average number of keywords typed
Search query types and user behaviour (e.g. time spend on SERP)
Search engine click bias
Why heatmaps suck and why scanpaths rock my world
Attractive, clickable keywords for metadata
Why aggregated, universal, blended, SERPs exist
Presentation of results and scanning behaviour
Snippet length and information processing
Search behaviours (e.g. pearl growth)
Male vs female search behaviours
Age
Reading time
Mobile, the environment and search
Trading channel data for campaign success brighton seoCrafted
Emma Andrews, Strategy Director at Crafted, outlines why inter-departmental collaboration is key to online marketing success. She explores how SEO data can be used to inform more effective channel strategy and discusses what SEOs can learn from the insights provided by other business units. Presented at BrightonSEO 2015
Google Shopping is one of the most talked about AdWords features at the moment but if you don't know what you are doing, you can waste a lot of budget and not get the ROI you were expecting.
In this presentation from BrightonSEO in 2015, you will find lots of tips and advice for making the most out of this platform and really competing in this competitive space.
How to Reverse Engineer Content - Paddy MooganPaddy Moogan
A process from Paddy Moogan on how to reverse engineer successful content and learn what you can do to increase the chances of your own content being successful.
Your Content is Awesome – Now What? By @staceycav at #brightonseoStacey MacNaught
Awesome content doesn’t, by default, mean successful content. In this #brightonseo talk, Stacey MacNaught talks content promotion tactics, approaches and tools to get your content seen and hit objectives.
How to have less rubbish ideas #brightonseoKelvin Newman
The document discusses how to generate better ideas by understanding your context, using reliable creative methods, and creating the right environment. It provides three stories as examples: 1) How a town called Scunthorpe had issues with AOL due to its name, highlighting the importance of context. 2) How computer circuits evolved to solve problems in unexpected ways, relating this to how search engines work. 3) How creating the right environment, even something simple like a different desk, can help ideas evolve. The overall message is that understanding constraints, applying techniques, and tweaking your surroundings can nudge you to think differently.
Google are pushing HTTPS hard. Why? And, when should you act? by Mark Thoma...SEO monitor
Google is pushing websites to adopt HTTPS to secure connections and provide encryption. The document discusses reasons for this, including privacy benefits and how some new browser features only work for secure HTTPS sites. It outlines challenges with migrating to HTTPS, including speed impacts and ensuring all site assets use HTTPS. HTTP/2 is presented as the next evolution, allowing more efficient use of network resources. Browser support for HTTP/2 is discussed, along with how it generally requires HTTPS for implementation.
Neil Walker from made Notable will discuss secure search, its past, impact and future. It was big news when Google first announced HTTPS as a ranking signal in August 2014, so what impact has this had for businesses, should brands and webmaster update to https and what tools and advise is needed to ensure a website meet Google’s guidelines.
This webinar will cover:
1. History of Https
2. The impact – Winners & Losers
3. Tools and advice to help you switch
4. The future of https as a ranking signal
Http to Https Get your WordPress website Compliant!Lynn Dye
It's nearly October of 2017 and if your WordPress website does not have an SSL certificate along with the accompanying secure content, updated URL on your website and edited .htaccess file to be in compliance, you don't have much time.
Google has announced that in October, 2017, they will start showing people a big, fat 'insecure' warning when people are using their Chrome browser and trying to fill out a contact form.
WordCamp US: Delivering the news over HTTPSPaul Schreiber
HTTP is dead. Here’s why, and what you need to know to migrate to HTTPS.
Delivered to WordCamp US in Philadelphia on December 5, 2015.
Detailed guide: https://docs.google.com/document/d/1EJKAoa4Hxc4AyH0znuA_AAplcNeNejEhATFptFX-OME/edit
Https Webinar slides - SEMRush with Gerry White, Tom Bourlet & Andy VealGerry White
Slides to accompany the webinar SEMrush hosted on HTTPS migrations, for more information on this go to htttps://www.takeitoffline.co.uk/https and to see more awesome webinars & blog posts from SEMrush visit https://www.semrush.com/webinars/
This document provides recommendations for migrating a website from HTTP to HTTPS. It recommends testing the SSL certificate, setting up Google Search Console access for HTTPS, running HTTP and HTTPS simultaneously, tracking in Google Analytics using Google Tag Manager, checking all templates and mobile versions render correctly, monitoring for mixed content exceptions, setting up a site audit in SEMRush, redirecting canonical tags and sitemaps after testing, implementing 301 redirects, enabling HTTP Strict Transport Security (HSTS), and addressing potential issues like images or embeds loaded insecurely. It emphasizes a gradual, step-by-step approach to ensure minimal risk in migrating to HTTPS.
SEO Considerations When Migrating to HTTPS by Kenneth SytianGlen Dimaandal
Kenneth Sytian's presentation at PeepCon. This is a guide on how SEOs and marketers can migrate their sites from HTTP to HTTPS for better security and ranking gains.
Lots of websites — from Wikipedia to Reddit to the Washington Post — are moving towards encrypting all of their web traffic to protect their readers' privacy. We'll talk about what this all means (benefits, downsides) and problems we've encountered moving to HTTPS (and how we solved them).
After 16 years of solid use, the HTTP protocol finally got a major update this year. HTTP is the standard that defines how computers communicate over the Internet, and had not changed since 1999. The modern web, however, has become much more complex and HTTP/2 helps to address this brave new world.
Watch the webinar on demand: https://www.nginx.com/resources/webinars/whats-new-in-http2/
SearchLove San Diego 2018 | Mat Clayton | Site Speed for Digital MarketersDistilled
We all know that site speed matters not only for users but also for search rankings. As marketers, how can we measure and improve the impact of site speed? Mat will cover a range of topics and tools, from the basic quick wins to some of the more surprising and cutting-edge techniques used by the largest websites in the world.
Planning Your Migration to SharePoint Online #SPBiz60Christian Buckley
Session from SPBiz.com online event on June 18th, 2015. It’s always best to begin with a plan, and this session will provide a framework for developing your own migration plan. While tools will help automate some aspects of the content move, much of the complexity of a SharePoint migration happens before a tool is installed. This session will help analysts, project managers and admin of SharePoint to reduce migration time and increase success.
Future of Search Engine Factors, AMP, On-Page Key to SuccessAnetwork
Farid Asadi introduces himself as an inbound marketing manager and UI/UX designer who is interested in SEO and Google Analytics. The document then provides information on key ranking factors for search engines, both currently and how they are predicted to change in the future. It emphasizes factors like mobile friendliness, structured data, site speed, HTTPS usage, and Accelerated Mobile Pages. The document concludes with tips on on-page SEO best practices like keyword targeting strategies and fulfilling user intent.
HTTPS & HTTP/2
This document discusses securing websites with HTTPS and migrating to HTTP/2. It provides guidance on setting up HTTPS with self-signed or free certificates. HTTP/2 improves performance over HTTPS compared to HTTP/1.1 by enabling features like server push and multiplexing. The document recommends securing all website content and resources with HTTPS to future-proof sites and unlock new browser capabilities. It also discusses optimizing for HTTPS and HTTP/2 by redirecting HTTP to HTTPS, enabling HTTP/2 via a CDN, and using HSTS.
What will happen to SEO ranking factors in 12 months? with some useful tools which you can use them for your business and improve your website in SERPs.
What will happen to SEO ranking factors in 12 months? with some useful tools which you can use them for your business and improve your website in SERPs.
Google uses more than 200 factors to rank website. Security is going to add in this list. According to experts, Google may use security as a new ranking factor in near future.
Prof. Erwin M. Globio gave a presentation on HTML5 that covered:
1) The history and development of HTML5 by groups like WHATWG and its adoption by W3C.
2) New features in HTML5 like audio, video, and canvas elements to enable richer content as well as geo-location APIs for mobile apps.
3) Issues with older standards like HTML4 and XHTML2 that HTML5 aims to address and improve cross-browser compatibility.
4) Questions around browser support for HTML5 and implications for web designers in adopting the new standard.
This memorandum from the Federal Chief Information Officer requires all publicly accessible federal websites and web services to only provide service through secure HTTPS connections by December 31, 2016. It expands on prior guidance to improve privacy and security by encrypting data transmission and verifying website identities. While HTTPS adoption has costs, the policy aims to establish a consistent, private browsing experience for the public and position the government as a leader in internet security.
Similar to BrightonSEO Sep 2015 - HTTPS | Mark Thomas (20)
Amazon Aurora 클러스터를 초당 수백만 건의 쓰기 트랜잭션으로 확장하고 페타바이트 규모의 데이터를 관리할 수 있으며, 사용자 지정 애플리케이션 로직을 생성하거나 여러 데이터베이스를 관리할 필요 없이 Aurora에서 관계형 데이터베이스 워크로드를 단일 Aurora 라이터 인스턴스의 한도 이상으로 확장할 수 있는 Amazon Aurora Limitless Database를 소개합니다.
Airline Satisfaction Project using Azure
This presentation is created as a foundation of understanding and comparing data science/machine learning solutions made in Python notebooks locally and on Azure cloud, as a part of Course DP-100 - Designing and Implementing a Data Science Solution on Azure.
### Data Description and Analysis Summary for Presentation
#### 1. **Importing Libraries**
Libraries used:
- `pandas`, `numpy`: Data manipulation
- `matplotlib`, `seaborn`: Data visualization
- `scikit-learn`: Machine learning utilities
- `statsmodels`, `pmdarima`: Statistical modeling
- `keras`: Deep learning models
#### 2. **Loading and Exploring the Dataset**
**Dataset Overview:**
- **Source:** CSV file (`mumbai-monthly-rains.csv`)
- **Columns:**
- `Year`: The year of the recorded data.
- `Jan` to `Dec`: Monthly rainfall data.
- `Total`: Total annual rainfall.
**Initial Data Checks:**
- Displayed first few rows.
- Summary statistics (mean, standard deviation, min, max).
- Checked for missing values.
- Verified data types.
**Visualizations:**
- **Annual Rainfall Time Series:** Trends in annual rainfall over the years.
- **Monthly Rainfall Over Years:** Patterns and variations in monthly rainfall.
- **Yearly Total Rainfall Distribution:** Distribution and frequency of annual rainfall.
- **Box Plots for Monthly Data:** Spread and outliers in monthly rainfall.
- **Correlation Matrix of Monthly Rainfall:** Relationships between different months' rainfall.
#### 3. **Data Transformation**
**Steps:**
- Ensured 'Year' column is of integer type.
- Created a datetime index.
- Converted monthly data to a time series format.
- Created lag features to capture past values.
- Generated rolling statistics (mean, standard deviation) for different window sizes.
- Added seasonal indicators (dummy variables for months).
- Dropped rows with NaN values.
**Result:**
- Transformed dataset with additional features ready for time series analysis.
#### 4. **Data Splitting**
**Procedure:**
- Split the data into features (`X`) and target (`y`).
- Further split into training (80%) and testing (20%) sets without shuffling to preserve time series order.
**Result:**
- Training set: `(X_train, y_train)`
- Testing set: `(X_test, y_test)`
#### 5. **Automated Hyperparameter Tuning**
**Tool Used:** `pmdarima`
- Automatically selected the best parameters for the SARIMA model.
- Evaluated using metrics such as AIC and BIC.
**Output:**
- Best SARIMA model parameters and statistical summary.
#### 6. **SARIMA Model**
**Steps:**
- Fit the SARIMA model using the training data.
- Evaluated on both training and testing sets using MAE and RMSE.
**Output:**
- **Train MAE:** Indicates accuracy on training data.
- **Test MAE:** Indicates accuracy on unseen data.
- **Train RMSE:** Measures average error magnitude on training data.
- **Test RMSE:** Measures average error magnitude on testing data.
#### 7. **LSTM Model**
**Preparation:**
- Reshaped data for LSTM input.
- Converted data to `float32`.
**Model Building and Training:**
- Built an LSTM model with one LSTM layer and one Dense layer.
- Trained the model on the training data.
**Evaluation:**
- Evaluated on both training and testing sets using MAE and RMSE.
**Output:**
- **Train MAE:** Accuracy on training data.
- **T
4. “Individually, the meta data you can gather from
unencrypted sites can seem benign, when you put
it all together it uncovers a lot about my intent and
can actually compromise privacy.” Ilya Grigorik
6. Maile Ohye SMX Advanced 2015
HTTPS benefits:
• Authenticates the site
• Grants data integrity for the client
• Gives encryption which is good for the user
“For new and particularly powerful web platform
features, browser vendors prefer to make the
feature available only to secure origins by default.”
Sounds
interesting!!!!
7. August 2014
“Making the
internet safer more
broadly”
“Over time, we
may decide to
strengthen it.”
“It’s only a very
lightweight signal”
10. Growing trend
towards HTTPS
5%
6%
7%
8%
9%
10%
Jan March April May June July August
% Alexa Top 100K Websites on HTTPS (2015), DeepCrawl
0%
20%
40%
60%
80%
100%
Jan March April May June July August
% Alexa Top 100K Websites HTTPS/HTTP, DeepCrawl
HTTPS HTTP
Opportunity
18. • Speed - HTTPS runs slower than HTTP
• All resources (JS, CSS, images) need to be on HTTPS.
• Internal links, Sitemaps, canonical tags, robots.txt file and analytics
tracking codes need to be updated to refer to HTTPS version.
• 302 redirects not a clear enough signal that the site has moved to
HTTPS. Google specifically state that 301 redirects should be used.
• Avoid redirect chains – avoid latency
• HSTS not enabled in addition to HTTPS
• Might incur issues with third-party resources (e.g. ad networks)
• Analytics and backlink data could be affected.
• Social shares also need to be migrated/managed to retain social proof
(only Facebook, Google +1 and LinkedIn shares transfer automatically,
although this can still take weeks/months).
22. When should you migrate?
New Websites: Definitely build on HTTPS
Existing Websites: Migrate to HTTPS when you’re
next planning a domain migration
Or,
Build the infrastructure to support
HTTPS during a site
redevelopment for a later URL
migration
32. What is HTTP/2?
HTTP/2 (originally named HTTP/2.0) is the second major
version of the HTTP network protocol used by the World
Wide Web. It is based on SPDY.
HTTP 1 was designed for webpages with few external
assets. Browsers typically downloaded assets
sequentially, but this wasn’t a problem on lighter pages.
Now most webpages have 50+ resources, which is
difficult for HTTP 1 to handle.
HTTP/2 downloads many resources at the same time,
prioritizes them and supports compressed HTTP headers.
https://http2.github.io/
33. The proposed changes do not require any changes to how existing
web applications work, but new applications can take advantage of
new features for increased speed.
HTTP/2 allows the server to "push" content, that is, to respond with
data for more queries than the client requested.
HTTP/2 enables a more efficient use of network resources and a
reduced perception of latency by introducing header field
compression and allowing multiple concurrent exchanges on the
same connection. It also introduces unsolicited push of
representations from servers to clients.
This specification is an alternative to, but does not obsolete, the
HTTP/1.1 message syntax. HTTP's existing semantics remain
unchanged.
Googlebot did not (as of June 2nd 2015) support HTTP/2
https://http2.github.io/
38. HTTP/2 and HTTPS
“Although the standard itself does not require
usage of encryption, most client implementations
(Firefox, Chrome) have stated that they will only
support HTTP/2 over TLS, which makes
encryption de facto mandatory.”
https://en.wikipedia.org/wiki/HTTP/2
This talk is going to focus on HTTPS, the challenges people are facing when migrating and why you should be planning your migration.
Web Search & Chrome Team
Security benefits are clear – public WIFI is inherently risky
August 2014 – Lightweight Signal but May Strengthen
Common sense approach – to allow webmasters time to migrate
Common sense approach – to allow webmasters time to migrate
Other benefit as highlighted by Moz confirms when traffic passes to an HTTPS site, the secure referral information is preserved rather than stripped away and shown up as “direct” https://moz.com/blog/seo-tips-https-ssl
I’m afraid I’m not going to sensationalise this issue – as tempting as it has been for several commentators. We’re going to take a look at what Google actually had to say, where people are struggling at present, and some pointers to help you make this as painless as possible.
Built with indicates a figure around 6% - slightly different methodology to DeepCrawl but safe to assume somewhere between 6%-9%: http://trends.builtwith.com/ssl/SSL-by-Default
As with any site migration, prepare for a drop in rankings/traffic in the short-term -
Did they forget to move their disavow file when they migrated? I can only conclude that a penalty of this magnitude must have been a Penguin related incident.
When you’ve got your disavow file uploaded and you are moving to a new domain, your disavow file is not automatically moved to HTTPS. Therefore, if you don’t upload your disavow file to the HTTPS version of Google Webmaster Tools, it is not taken into consideration and you risk being hit with a Manual Penalty or by Google Penguin.
Here’s a quick selection of issues. It is technically demanding - lots of moving parts.
I’m not sure this was even possible last August.
It's also just a lot of work, and very the best you can hope for is to see no change.
Let’s return to the story, where are we now?
Guilting people into a change 12 months on from a controlled announcement.
You have to take into account that the ad-networks can’t serve everything completely.
HTTP 1 is showing it’s age. Many of us spent countless hours attempting to optimising images and so forth. This will represent a step change – fit for purpose.
SPDY was designed by Google – approved by Facebook
SPDY was designed by Google – approved by Facebook
Has now been passed as an RFC.
Enable HTTP/2 – making the page load times much better but not just for the user but also on the server. Fewer handshakes, fewer sockets, fewer buffers = less memory and workload – decreasing ops costs
HTTP/2 is supported by the most current releases of Firefox and Chrome.