Social Media

Euro Betting

Betting on the EUROs is now due to COVID even more online than ever before. Due to the COVID restriction Betting shops were closed and this forced people to BET online and now with the EUROS 2020 / 2021 companies like BOB Sports / BOB88 have seen a huge increase in demand.

The EURO’s is running from 11th June 2021 to 11th July 2021 with 11 host cities staging the 51 fixtures.

 

 

EUROS Betting

The best thing about EUROs betting online is that you can use the accumulator and mix bets. BOB Sports also provides gifts as you add more bets into the accumulator which is great:-

To make a EURO bet simply visit https://www.bob88.co.uk/sports/football/euro-2020/

Google’s Core Web Vitals is coming in May 2021

To succeed in SEO you have to pay attention to the changes likely to make an impact on a website’s rankings and it is not very often Google let you know what they are doing. The fact that they have announced a release of “Google’s Core Web Vitals Update” which is to be released in May 2021 means we need to understand this change.

The fact that Google has given Digital Marketing consultants time to prepare is unprecedented.

Google Core Web Vitals report

The Gogole Core Web Vitals update is aimed at fixing poor user experiences on websites, to drive a positive change to the Internet. On The Google support page https://support.google.com/webmasters/answer/9205520?hl=en it explains the reasons behind this change.

Why page performance matters
  • Longer page load times have a severe effect on bounce rates. For example:
    • If page load time increases from 1 second to 3 seconds, bounce rate increases 32%
    • If page load time increases from 1 second to 6 seconds, bounce rate increases by 106%
  • Read case studies here.

In Google Search Console under enhancements there is now available “Core web Vitals”.

 

Google Core Web Vitals in Search Console

If you visit Google Search Console and take a look at a report you will find the issues now highlighted and an SEO Company can start to fix these. Interestingly when you look at the reports the data being captured goes back to November 2020, so it is clear that this drive for evaluating page experience for a better web has been fully active for some time now.

Google’s note on timing: “We recognize many site owners are rightfully placing their focus on responding to the effects of COVID-19. The ranking changes described in this post will not happen before next year, and we will provide at least six months notice before they’re rolled out. We’re providing the tools now to get you started (and because site owners have consistently requested to know about ranking changes as early as possible), but there is no immediate need to take action.

 

 

Google Core Web Vitals Report

It is important to to understand what is the main driver behind this core change and loading interactivity and visual stability is the main focus of this update in t4erms of search signals for page experience.

 

Google Core Web Vitals how to

It is clear that Google has driven this change to force website owners to think about page experience including this as a core ranking factor. We believe this is a good move because the page experience of visitors enables people to get more done and engage more deeply with the website.

In contrast, a bad page experience could prevent a person being able to find the valuable information on a website. Google’s drive to force website owners to focus on page experience as part of the signals being used when the algorithm considers a websites worth to be included in search results means that website visitors will more easily be able to access the information they are looking for.

 

Google Core Web Vitals Report Data Sources

This new update is taking data for the Core Web Vitals report from the Chrome User Experience Report known as the CrUX report which provides user experience metrics for how real-world Chrome users experience websites.

The Chrome User Experience Report is powered by real user measurement of key user experience metrics across the public web, aggregated from users who have opted-in to syncing their browsing history, have not set up a Sync passphrase, and have usage statistic reporting enabled. 

The data from the CrUX is made available via:

  1. PageSpeed Insights, which provides URL-level user experience metrics for popular URLs that are known by Google’s web crawlers.
  2. Public Google BigQuery project, which aggregates user experience metrics by origin, for all origins that are known by Google’s web crawlers, and split across multiple dimensions outlined below.

The CrUX report gathers anonymized metrics about performance times from actual users visiting your URL (called field data). The CrUX database gathers information about URLs whether or not the URL is part of a Search Console property. The metrics provided by the public Chrome User Experience Report hosted on Google BigQuery are powered by standard web platform APIs exposed by modern browsers and aggregated to origin-resolution. Site owners that want more detailed (URL level resolution) analysis and insight into their site performance and can use the same APIs to gather detailed real user measurement (RUM) data for their own origins.

 

 

We have been testing and found some strange issues with the results being detected. For example on a webpage that was loading qucik in a browser we ran the reports and foudn the issue to be:-

Reduce the impact of third-party code Third-party code blocked the main thread for 3,590 ms

 

This shows the issue to be Google Recaptcha software and  the fact as CDN is used to speed up the website?

Minimize main-thread work 11.6 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

 

The website being test has Adsense on it and Google Analytics with very little scripting so the issue is something outside of the web developers control.

Reduce JavaScript execution time 8.2 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.

 

So on investigation again this is Google’s recaptcha causing the issue!

Serve static assets with an efficient cache policy 18 resources found

A long cache lifetime can speed up repeat visits to your page. 

So again on investigation the issue is Google Analytics and Recaptcha which a developer cannot control.

Avoid enormous network payloads Total size was 4,017 KiB

Large network payloads cost users real money and are highly correlated with long load times.

So investigation shows the issues again to be Google Recaptcha and Analytics which cannot be changed by a developer.

First Paint

Defined by the Paint Timing API and available in Chrome M60+:

“First Paint reports the time when the browser first rendered after navigation. This excludes the default background paint, but includes non-default background paint. This is the first key moment developers care about in page load – when the browser has started to render the page.”

First Contentful Paint

Defined by the Paint Timing API and available in Chrome M60+:

“First Contentful Paint reports the time when the browser first rendered any text, image (including background images), non-white canvas or SVG. This includes text with pending webfonts. This is the first time users could start consuming page content.”

DOMContentLoaded

Defined by the HTML specification:

“The DOMContentLoaded reports the time when the initial HTML document has been completely loaded and parsed, without waiting for stylesheets, images, and subframes to finish loading.” – MDN.

onload

Defined by the HTML specification:

“The load event is fired when the page and its dependent resources have finished loading.” – MDN.

First Input Delay

“First Input Delay (FID) is an important, user-centric metric for measuring load responsiveness because it quantifies the experience users feel when trying to interact with unresponsive pages—a low FID helps ensure that the page is usable.” – web.dev/fid/

Largest Contentful Paint

“Largest Contentful Paint (LCP) is an important, user-centric metric for measuring perceived load speed because it marks the point in the page load timeline when the page’s main content has likely loaded—a fast LCP helps reassure the user that the page is useful.” – web.dev/lcp/

Cumulative Layout Shift

“Cumulative Layout Shift (CLS) is an important, user-centric metric for measuring visual stability because it helps quantify how often users experience unexpected layout shifts—a low CLS helps ensure that the page is delightful.” – web.dev/cls/

Time to First Byte

“Time to first byte (TTFB) is a measurement used as an indication of the responsiveness of a webserver or other network resource. TTFB measures the duration from the user or client making an HTTP request to the first byte of the page being received by the client’s browser. This time is made up of the socket connection time, the time taken to send the HTTP request, and the time taken to get the first byte of the page.” – Wikipedia

Notification Permissions

Defined by the Notifications API and explained by MDN:

“The Notifications API allows web pages to control the display of system notifications to the end user. These are outside the top-level browsing context viewport, so therefore can be displayed even when the user has switched tabs or moved to a different app. The API is designed to be compatible with existing notification systems, across different platforms.” – MDN

Chrome will show users a prompt to grant the active website permission to show notifications when initiated by the website. Users can take actively or passively take one of four actions:

  • Accept
    • If the user has explicitly allowed the website to show them notifications.
  • Deny
    • If the user has explicitly disallowed the website from showing them notifications.
  • Dismiss
    • If the user closes the permission prompt without giving any explicit response.
  • Ignore
    • If the user does not interact with the prompt at all.

Dimensions

Performance of web content can vary significantly based on device type, properties of the network, and other variables. To help segment and understand user experience across such key segments, the Chrome User Experience Report provides the following dimensions.

Effective Connection Type

Defined by the Network Information API and available in Chrome M62+:

“Provides the effective connection type (“slow-2g”, “2g”, “3g”, “4g”, or “offline”) as determined by round-trip and bandwidth values based on real user measurement observations.”

Device Type

Coarse device classification (“phone”, “tablet”, or “desktop”), as communicated via User-Agent.

Country

Geographic location of users at the country-level, inferred by their IP address. Countries are identified by their respective ISO 3166-1 alpha-2 codes.

Data format

The report is provided via Google BigQuery as a collection of datasets containing user experience metrics aggregated to origin-resolution. Each dataset represents a single country, country_rs captures user experience data for users in Serbia (rs is the ISO 31611-1 code for Serbia). Additionally, there is a globally aggregated dataset (all) that captures the world-wide experience. Each row in the dataset contains a nested record of user experience for a particular origin, split by key dimensions.

Dimension
origin“https://example.com”
effective_connection_type.name4G
form_factor.name“phone”
first_paint.histogram.start1000
first_paint.histogram.end1200
first_paint.histogram.density0.123

For example, the above shows a sample record from the Chrome User Experience Report, which indicates that 12.3% of page loads had a “first paint time” measurement in the range of 1000-1200 milliseconds when loading “http://example.com” on a “phone” device over a ”4G”-like connection. To obtain a cumulative value of users experiencing a first paint time below 1200 milliseconds, you can add up all records whose histogram’s “end” value is less than or equal to 1200.

Status: Poor, Need improvement, Good

The labels Poor, Needs improvement, and Good are applied to a URL on specific device type.

URL status
A URL’s status is the slowest status assigned to it for that device type. So:

A URL on mobile with Poor FID but Needs improvement LCP is labeled Poor on mobile.
A URL on mobile with Needs improvement LCP but Good FID is labeled Needs improvement on mobile.
A URL on mobile with Good FID and CLS but no LCP data is considered Good on mobile.
A URL with Good FID, LCP, and CLS on mobile and Needs improvement FID, LCP, and CLS on desktop is Good on mobile and Needs improvement on desktop.
If a URL has less than a threshold of data for a given metric, that metric is omitted from the report for that URL. A URL with data in only one metric is assigned the status of that metric. A URL without threshold data for either metric will not be on the report.

Status definitions
Status metrics are evaluated against the following boundaries:

Status definitions

Status metrics are evaluated against the following boundaries:

 GoodNeeds improvementPoor
LCP<=2.5s<=4s>4s
FID<=100ms<=300ms>300ms
CLS<=0.1<=0.25>0.25
  • LCP (largest contentful paint): The amount of time to render the largest content element visible in the viewport, from when the user requests the URL. The largest element is typically an image or video, or perhaps a large block-level text element. This is important because it tells the reader that the URL is actually loading.
    • Agg LCP (aggregated LCP) shown in the report is the time it takes for 75% of the visits to a URL in the group to reach the LCP state.
  • FID (first input delay): The time from when a user first interacts with your page (when they clicked a link, tapped on a button, and so on) to the time when the browser responds to that interaction. This measurement is taken from whatever interactive element that the user first clicks. This is important on pages where the user needs to do something, because this is when the page has become interactive.
    • Agg FID (aggregated FID) shown in the report means that 75% of visits to a URL in this group had this value or better.
  • CLS (Cumulative Layout Shift): The amount that the page layout shifts during the loading phase. The score is rated from 0–1, where zero means no shifting and 1 means the most shifting. This is important because having pages elements shift while a user is trying to interact with it is a bad user experience.
    • Agg CLS (aggregated CLS) shown in the report is the lowest common CLS for 75% of visits to a URL in the group.
ALDI Can Brew Dog

BrewDog vs Aldi

covid19 equipped

Covid 19 Equipped

covid19equipped.com donation support needed

Proud to be supporting Covid 19 Equipped helping health professionals get the PPE they need to combat the COVID 19 Virus.

https://www.covid19equipped.com/

All of your generous donation will go towards the purchase and supply of masks and other PPE (Personal Protective Equipment) for use by our essential workers

.uk Rights of Registration

The .uk Right of Registration period ended on 25th June 2019.

All registrars who applied to be part of the release process and met the criteria to participate were contacted by Nominet via email on Wednesday 26th June with their allocation.

The final list of domains was published on 26th June. Those domains were made available in batches from the 1st of July- 5th July to participating registrars. This phase of the release process is now complete.

Domains still available after the stage one release will become generally available from 8th July for any registrar to register, including those using WDM.

What is the ‘release’ process?

It is the release of .uk domains where rights were not exercised by the deadline date and the domain can now be registered by someone other than the rights holder.

What is happening to the unclaimed .uk rights?

Reserved .uk domain names which were not registered by 25th June 2019 at 06:00 BST (UTC+1) were subject to a first phase release process that took place between 1st July and 5th July 2019.

Participating registrars were informed.

Any domains not registered during this period are available to all registrars via normal systems (EPP and WDM) from 8th July.

When will the domains become generally available using the standard .UK EPP and WDM?

Domains that were not registered in batch 1 (from 1st July) will become generally available through the standard .UK EPP connection and WDM one week later, i.e. on 8th July between 14.00 and 14:30 BST (UTC+1).  Batch 2 on 9th July during the same time period, batch 3 on 10th July etc.

The release schedule for Stage Two is as follows:

8th July – Batch 1: Domains beginning 0-9, a-b
9th July – Batch 2: Domains beginning c-f
10th July – Batch 3: Domains beginning g-m
11th July – Batch 4: Domains beginning n-s
12th July – Batch 5: Domains beginning t-z

Once the domains become available, they will then remain available until registered.

There is no sign-up process to take part in stage two of the release. This is a general release between 8th July and 12th July via the normal EPP and WDM systems.

Has Nominet run any awareness activity to registrants?

We ran a series of awareness activities on the lead up to 25th June targeting a broad business and consumer audience, influencers and selected vertical sectors. Our awareness campaign included national press and radio, tube advertising, social media and PR.

Has Nominet contacted registrants directly before the 25th June deadline?

We contacted registrants during the reservation period, including some targeted outreach in recent months. We wanted registrants to be aware that they had a right to their corresponding .uk domain, without feeling pressured into registering a domain they did not want.

Over the last five years our direct communications have included emailing or sending letters to rights holders. Most recently, we did this if we were unsure whether rights holders had received sufficient communication from their registrar.

A series of promotions were available to registrars to encourage take-up, supported by toolkits to support registrar messaging.

The following FAQs are all specific to stage one of the release process that happened between 1stJuly and 5th July 2019.

Can I sign up now? 

The deadline for participating registrars to meet the release process criteria for the main release phase has ended.  Unfortunately, registrars that did not sign up or meet the criteria were not be able to participate directly in the first phase of the release.

Where a RoR domain name is not registered through the main release phase 1st – 5th July, it will be available to register through the standard registration systems seven days later.

When will the release process take place?

The rights period ended on 25th June 2019 at 06:00 BST (UTC+1). The domains begin to be available to register from 1st July 2019.

What was the process for signing up to participate in the release process?

Registrars were given the opportunity to sign up to take part from 8th April to 3rd May 2019. The sign up has now closed and only those who registered by the deadline and have met certain criteria were able to participate in the release.

If I signed up to the release should I have received a confirmation email?

Yes, every registrar who signed up should have received a confirmation email on Friday 10th May. The email was sent to the email address as indicated by each registrar during the sign–up process. All registrars who signed up to participate have since been emailed on 26th June to confirm whether they met the criteria, and if so, their allocation of registration requests.

What is the mechanism for the rights release?

Registration of released domains during the release period (1st – 5th July) could only be made through a separate Right of Registration EPP connection. Those registrars who have signed up to the release and have met the criteria to participate were able to use the Right of Registration EPP connection to register the .uk domains.

EPP is instant and responses are received in near real time. As such we have chosen to provide an EPP mechanism that supports domains to be released in a manner that protects systems and ensures continuity of service for normal domain name operations. We provided advanced notice of the release mechanism so registrars who only use Web Domain Manager have had opportunity to arrange to use EPP.

What credit had to be met in order to participate?

Registrars needed to ensure that they had sufficient credit available to qualify for their tier. Remaining credit can be viewed within Online Services via the Billing Summary.

The amount of available credit also needed to take into account any normal registration and renewal levels.

We asked that any funds added to an account to increase the available credit were done well in advance of the 21st June. If funds were added via BACS, we asked that registrars included a reference such as account number and ‘RoR’ so we could ensure it was allocated to the relevant account in time.

Registrars were given the opportunity to also ask for an increase in their credit limit for the duration of the release to ensure that they could meet their anticipated demand.

*This figure was in addition to registrar standard registration and renewal activity and only applied to Nominet members. Non-members were asked to deposit multiples of the £80 +VAT registration fee per domain, per two–year registration. Minimum available credit figures include VAT​. For those who don’t pay VAT, registrars were only required to have the amount on the account as specified minus VAT.

How were allocations/registration requests decided?

To ensure the stability and reliability of our systems a finite number of registration requests per minute were available.

Our approach was to allocate a registrar to a tier that corresponded to the number of registrations they indicated they would be pursuing.  Registrars were asked to ensure sufficient funds were available to secure access to each tier.

We applied a 5% tolerance to the credit limits (reflecting a registrar’s ability to delete up to 5% or 5 domains, whichever is higher, prior to invoicing), and where available credit still falls short, we allocated the registrar to the next appropriate tier.

Are the requests per minute the same as originally set out?

The allocations were subject to take up and the number of qualifying registrars.  For the top tier, the requests for registration per minute remained at 150.  For tiers 2, 3 and 4, they increased to 75, 12 and 9 requests per minute respectively.

Is that different to the original approach?

We specified that only registrars who met the following criteria would be able to connect to the release system via a dedicated EPP connection:

  1. Had sufficient available credit on their account for their original allocated tier by Midday BST (UTC+1) on the 21st June​
  2. Connected to the .uk testbed and performed a login, contact create and a domain create operation against any domain

Our team got in touch with registrars who applied to help as many as possible take part in the release.

In what order were the domains released?

All domains with rights that were not registered by the rights holder were put into five batches in alphabetical order. Each batch was released at 14:00 BST (UTC+1) from 1st July to 5th July 2019.  All domains in a batch became available at the same time (14.00 BST UTC+1). Once the domain became available during the release period it then remained available throughout the release period.

The release date and time for each domain name with expired rights was available in Online Services on 26th June.

The release schedule is as follows:

Batch 1: Domains beginning 0-9, a-b

Batch 2: Domains beginning c-f

Batch 3: Domains beginning g-m

Batch 4: Domains beginning n-s

Batch 5: Domains beginning t-z

Domains released in batch 1 (1st July) became generally available through the standard .UK EPP connection and WDM one week later, i.e. on 8th July between 14.00 and 14:30 BST (UTC+1).  Batch 2 on 9th July, batch 3 on 10th July etc.