Loblaw.Ca loblaw.ca

Stas.Loblaw.Ca

stas.loblaw.ca receives about 28,125 unique visitors and 56,249 (2.00 per visitor) page views per day which should earn about $357.03/day from advertising revenue. Estimated site value is $260,628.29. According to Alexa Traffic Rank stas.loblaw.ca is ranked number 116,627 in the world and 0.00062% of global Internet users visit it. Site is hosted in Cambridge, Massachusetts, 02142, United States and links to network IP address 104.127.0.63. This server supports HTTPS and doesn't support HTTP/2.

About - stas.loblaw.ca

Distributeur alimentaire, Profil et relations avec les investisseurs, emplacements des magasins et occasions d'emploi.
Edit Site Info

Technologies used on Website

UI frameworks
Bootstrap
Analytics
Google Analytics
Font Scripts
Google Font API
Web Frameworks
Java Servlet
Programming Languages
Java

stas.loblaw.ca Profile

Title: My Schedule
Last update was 9 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with loblaw.ca in any way. Only publicly available statistics data are displayed.

How popular is stas.loblaw.ca?

28.1K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
28,125
Monthly Unique Visitors:
675,000
Pages per Visit:
2.00
Daily Pageviews:
56,249
Alexa Rank:
116,627 visit alexa
Alexa Reach:
0.00062%   (of global internet users)
Avg. visit duration:
03:02
Bounce rate:
43.78%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
27.72%
Referral:
30.79%
Search:
26.50%
Social:
4.00%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
Canada 80.2%78.6%2522
United States 8.4%7.3%162991

Where do visitors go on this site?

Reach%Pageviews%PerUser
loblaw.ca
54.00%52.07%1.8
stas.loblaw.ca
25.41%23.76%1.8
sts.loblaw.ca
24.06%12.64%1.0
OTHER
0%11.53%0

Competitive Data

SEMrush
Domain:
  stas.loblaw.ca
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  50
Page Authority:
  32
MozRank:
  3

+ How socially engaged is stas.loblaw.ca?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
loblaw.ca
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
loblaw.ca
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much stas.loblaw.ca can earn?

Daily Revenue:
$357.03
Monthly Revenue:
$10,710.90
Yearly Revenue:
$130,315.95
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Canada 44,212$309.92
United States 4,106$47.10

How much money do stas.loblaw.ca lose due to Adblock?

Daily Revenue Loss:
$85.96
Monthly Revenue Loss:
$2,578.76
Yearly Revenue Loss:
$31,374.90
Daily Pageviews Blocked:
11,792
Monthly Pageviews Blocked:
353,761
Yearly Pageviews Blocked:
4,304,095
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Canada 11,053$77.48
United States 739$8.48

How much is stas.loblaw.ca worth?

Website Value:
$260,628.29

+ Where is stas.loblaw.ca hosted?

Server IP:
104.127.0.63
ASN:
AS16625 
ISP:
Akamai Technologies, Inc. 
Server Location:
Cambridge
Massachusetts, MA
02142
United States, US
 

Other sites hosted on 104.127.0.63

There are no other sites hosted on this IP

+ How fast does stas.loblaw.ca load?

Average Load Time:
(729 ms) 89 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

96
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)1.6s 59% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 59% 31% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 31% 8% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 8%
First Input Delay (FID)13ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)1.6s 59% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 59% 31% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 31% 8% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 8%
First Input Delay (FID)13ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Eliminate render-blocking resources - Potential savings of 140 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://fonts.googleapis.com/css?family=Open+Sans+Condensed:300|Open+Sans
1 KB230
https://stas.loblaw.ca/lcl-employee-scheduler-ui/css/bootstrap.min.css
3 KB70
https://stas.loblaw.ca/lcl-employee-scheduler-ui/css/style.css
3 KB150
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://stas.loblaw.ca/
0 ms211 ms0 KB0 KB302
https://stas.loblaw.ca/
211 ms523 ms0 KB0 KB301text/html
https://stas.loblaw.ca/en/badgeid
523 ms648 ms2 KB3 KB200text/htmlDocument
https://fonts.googleapis.com/css?family=Open+Sans+Condensed:300|Open+Sans
660 ms672 ms1 KB5 KB200text/cssStylesheet
https://stas.loblaw.ca/lcl-employee-scheduler-ui/css/bootstrap.min.css
660 ms758 ms3 KB12 KB200text/cssStylesheet
https://stas.loblaw.ca/lcl-employee-scheduler-ui/css/style.css
661 ms702 ms3 KB10 KB200text/cssStylesheet
https://stas.loblaw.ca/lcl-employee-scheduler-ui/images/lcl-ajax-loader.gif
661 ms789 ms3 KB3 KB200image/gifImage
https://stas.loblaw.ca/lcl-employee-scheduler-ui/js/main.js
661 ms714 ms251 KB1191 KB200application/javascriptScript
https://stas.loblaw.ca/lcl-employee-scheduler-ui/css/fonts/Roboto/Roboto-Regular.ttf
906 ms1102 ms159 KB159 KB200application/x-font-ttfFont
https://stas.loblaw.ca/lcl-employee-scheduler-ui/images/arrow-right.png
918 ms1069 ms1 KB1 KB200image/pngImage
https://www.google-analytics.com/analytics.js
919 ms924 ms18 KB43 KB200text/javascriptScript
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=1228936070&t=pageview&_s=1&dl=https%3A%2F%2Fstas.loblaw.ca%2Fen%2Fbadgeid&ul=en-us&de=UTF-8&dt=My%20Schedule&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEAB~&jid=640062377&gjid=1725130003&cid=1037892463.1578347800&tid=UA-75695566-1&_gid=937716964.1578347800&_r=1&z=896267969
951 ms956 ms1 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://stas.loblaw.ca/lcl-employee-scheduler-ui/js/main.js
0 ms251 KB
https://stas.loblaw.ca/lcl-employee-scheduler-ui/css/fonts/Roboto/Roboto-Regular.ttf
0 ms159 KB
https://stas.loblaw.ca/lcl-employee-scheduler-ui/images/lcl-ajax-loader.gif
0 ms3 KB
https://stas.loblaw.ca/lcl-employee-scheduler-ui/images/arrow-right.png
0 ms1 KB
https://www.google-analytics.com/analytics.js
7200000 ms18 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
19 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
675 ms
7 ms
784 ms
160 ms
953 ms
23 ms
1127 ms
5 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://stas.loblaw.ca/lcl-employee-scheduler-ui/css/fonts/Roboto/Roboto-Regular.ttf
196 ms
JavaScript execution time - 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
https://stas.loblaw.ca/lcl-employee-scheduler-ui/js/main.js
151 ms115 ms20 ms
Defer offscreen images - Potential savings of 3 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

URL
SizePotential Savings
https://stas.loblaw.ca/lcl-employee-scheduler-ui/images/lcl-ajax-loader.gif
3 KB3 KB
Avoids enormous network payloads - Total size was 443 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://stas.loblaw.ca/lcl-employee-scheduler-ui/js/main.js
251 KB
https://stas.loblaw.ca/lcl-employee-scheduler-ui/css/fonts/Roboto/Roboto-Regular.ttf
159 KB
https://www.google-analytics.com/analytics.js
18 KB
https://stas.loblaw.ca/lcl-employee-scheduler-ui/css/bootstrap.min.css
3 KB
https://stas.loblaw.ca/lcl-employee-scheduler-ui/images/lcl-ajax-loader.gif
3 KB
https://stas.loblaw.ca/lcl-employee-scheduler-ui/css/style.css
3 KB
https://stas.loblaw.ca/en/badgeid
2 KB
https://stas.loblaw.ca/lcl-employee-scheduler-ui/images/arrow-right.png
1 KB
https://fonts.googleapis.com/css?family=Open+Sans+Condensed:300|Open+Sans
1 KB
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=1228936070&t=pageview&_s=1&dl=https%3A%2F%2Fstas.loblaw.ca%2Fen%2Fbadgeid&ul=en-us&de=UTF-8&dt=My%20Schedule&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEAB~&jid=640062377&gjid=1725130003&cid=1037892463.1578347800&tid=UA-75695566-1&_gid=937716964.1578347800&_r=1&z=896267969
1 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
141 ms
Other
26 ms
Script Parsing & Compilation
23 ms
Style & Layout
18 ms
Parse HTML & CSS
12 ms
Rendering
4 ms
Avoids an excessive DOM size - 43 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
43
Maximum DOM Depth
10
Maximum Child Elements
7
Minify JavaScript - Potential savings of 100 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
https://stas.loblaw.ca/lcl-employee-scheduler-ui/js/main.js
251 KB100 KB
Avoid multiple page redirects - Potential savings of 340 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://stas.loblaw.ca/)
0
https://stas.loblaw.ca/
190
https://stas.loblaw.ca/en/badgeid
150
Keep request counts low and transfer sizes small - 12 requests • 443 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
12443 KB
Script
2269 KB
Font
1159 KB
Stylesheet
38 KB
Image
35 KB
Document
12 KB
Other
21 KB
Media
00 KB
Third-party
320 KB
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 130 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)1.5s 59% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 61% 29% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 29% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)294ms 12% of loads for this page have a fast (<100ms) First Input Delay (FID) 12% 82% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 82% 4% of loads for this page have a slow (>300ms) First Input Delay (FID) 4%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)1.5s 58% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 58% 34% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 34% 7% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 7%
First Input Delay (FID)100ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 94% 4% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 4% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
First Contentful Paint (3G) 2160 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 15 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
15
Maximum DOM Depth
3
Maximum Child Elements
13
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://stas.loblaw.ca/)
0
https://stas.loblaw.ca/
630
Keep request counts low and transfer sizes small - 5 requests • 2 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
52 KB
Image
31 KB
Document
11 KB
Other
10 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://stas.loblaw.ca/
0 ms218 ms0 KB0 KB302
https://stas.loblaw.ca/
218 ms486 ms1 KB1 KB200text/htmlDocument
https://stas.loblaw.ca/icons/blank.gif
497 ms536 ms0 KB0 KB200image/gifImage
https://stas.loblaw.ca/icons/text.gif
498 ms537 ms0 KB0 KB200image/gifImage
https://stas.loblaw.ca/icons/image2.gif
498 ms636 ms0 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 3 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://stas.loblaw.ca/icons/image2.gif
0 ms0 KB
https://stas.loblaw.ca/icons/text.gif
0 ms0 KB
https://stas.loblaw.ca/icons/blank.gif
0 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
516 ms
7 ms
534 ms
7 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
106 ms8 ms4 ms
Avoids enormous network payloads - Total size was 2 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://stas.loblaw.ca/
1 KB
https://stas.loblaw.ca/icons/image2.gif
0 KB
https://stas.loblaw.ca/icons/text.gif
0 KB
https://stas.loblaw.ca/icons/blank.gif
0 KB
http://stas.loblaw.ca/
0 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Other
52 ms
Style & Layout
22 ms
Rendering
13 ms
Script Evaluation
8 ms
Parse HTML & CSS
7 ms
Script Parsing & Compilation
4 ms
Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 270 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

akamai_bak.txt and 6 others render only 6 pixels tall (16 CSS pixels) .
2017-05-15 04:43 0 and 2 others render only 6 pixels tall (16 CSS pixels) .

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="?C=N;O=D">Name</a> and 3 others are close to other tap targets .

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://stas.loblaw.ca/icons/blank.gif (expiration not specified)
https://stas.loblaw.ca/icons/image2.gif (expiration not specified)
https://stas.loblaw.ca/icons/text.gif (expiration not specified)

Reduce server response time

In our test, your server responded in 0.34 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
Optimize images
Your images are optimized. Learn more about optimizing images.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does stas.loblaw.ca use compression?

stas.loblaw.ca use gzip compression.
Original size: 3.04 KB
Compressed size: 1.19 KB
File reduced by: 1.85 KB (60%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  63
Vendor reliability:
  63
Privacy:
  63
Child safety:
  93

+ SSL Checker - SSL Certificate Verify

stas.loblaw.ca supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: erefill.yourhealthmattershere.ca
Organization: Loblaws Inc.
Location: Toronto, Ontario, CA
Issuer: GeoTrust RSA CA 2018
Valid from: Feb 10 00:00:00 2020 GMT
Valid until: Sep 16 12:00:00 2020 GMT
Authority: Is not a CA
Keysize:
Common Name: GeoTrust RSA CA 2018
Organization: DigiCert Inc, OU=www.digicert.com
Location: US
Issuer: DigiCert Global Root CA
Valid from: Nov 6 12:23:45 2017 GMT
Valid until: Nov 6 12:23:45 2027 GMT
Authority: Is a CA
Keysize: 2048 Bits
Common Name: DigiCert Global Root CA
Organization: DigiCert Inc, OU=www.digicert.com
Location: US
Issuer: DigiCert Global Root CA
Valid from: Nov 10 00:00:00 2006 GMT
Valid until: Nov 10 00:00:00 2031 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support

stas.loblaw.ca does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Commerce et économie/Gastronomie et alimentation

+ Http Header

Server: AkamaiGHost
Content-Length: 0
Location: https://stas.loblaw.ca/
Date: Thu, 26 Mar 2020 06:55:03 GMT
Connection: keep-alive

HTTP/1.1 301 Moved Permanently
Location: https://stas.loblaw.ca/en/badgeid
Content-Length: 241
Content-Type: text/html; charset=iso-8859-1
Date: Thu, 26 Mar 2020 06:55:03 GMT
Connection: keep-alive
Set-Cookie: staspr=STAS_KDC;path=/;
Set-Cookie: NSC_tubtqsls.mpcmbx.db_443=ffffffffc3a0aa1e45525d5f4f58455e445a4a423660;expires=Thu, 26-Mar-2020 07:01:03 GMT;path=/;secure;httponly

HTTP/1.1 200 OK
X-Powered-By: Servlet/3.0
Last-Modified: Wed, 13 Mar 2019 17:08:32 GMT
Cteonnt-Length: 3109
Content-Type: text/html
Content-Language: en-US
Cache-Control: private
Content-Encoding: gzip
Content-Length: 1219
Vary: Accept-Encoding
Date: Thu, 26 Mar 2020 06:55:03 GMT
Connection: keep-alive
Set-Cookie: staspr=STAS_KDC;path=/;
Set-Cookie: NSC_tubtqsls.mpcmbx.db_443=ffffffffc3a0aa1f45525d5f4f58455e445a4a423660;expires=Thu, 26-Mar-2020 07:01:03 GMT;path=/;secure;httponly

+ DNS Lookup

Type Ip Target TTL
CNAME san.yourhealthmattershere.ca.edgekey.net 296

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

Currently Not Available
Last update was 9 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with loblaw.ca in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

flingtrainer.com
36 secs
cielreveur.blogspot.com
54 secs
9jabee.com
1 min
cibaksolutions.com
1 min
moutamadris.men.gov.ma
1 min
***.com
2 mins
musichype.com.ng
4 mins
chyolka.ru
4 mins
malespank.net
4 mins
prediksihebat.top
4 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
stas.loblaw.ca widget