Tools & Wizards About Us
lipstickempire.ca screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    87% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

lipstickempire.ca

Edmonton Facial Memberships and More! - Lipstick Empire Laserspa

Page Load Speed

3.4 sec in total

First Response

76 ms

Resources Loaded

2.1 sec

Page Rendered

1.3 sec

lipstickempire.ca screenshot

About Website

Welcome to lipstickempire.ca homepage info - get ready to check Lipstick Empire best content right away, or after learning these important things about lipstickempire.ca

Lipstick Empire LaserSpa is a full-service Medical Spa located in the heart of Edmonton Book now at lipstickempire.ca

Visit lipstickempire.ca

Key Findings

We analyzed Lipstickempire.ca page load time and found that the first response time was 76 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

lipstickempire.ca performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value2.3 s

98/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

lipstickempire.ca

76 ms

lipstickempire.ca

193 ms

wp-emoji-release.min.js

36 ms

formidableforms.css

76 ms

style.min.css

91 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 76% of them (70 requests) were addressed to the original Lipstickempire.ca, 10% (9 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Lipstickempire.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (23%)

Content Size

6.6 MB

After Optimization

5.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lipstickempire.ca main page is 6.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 128.9 kB

  • Original 154.2 kB
  • After minification 148.1 kB
  • After compression 25.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 128.9 kB or 84% of the original size.

Image Optimization

-21%

Potential reduce by 1.3 MB

  • Original 6.0 MB
  • After minification 4.7 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Lipstick Empire needs image optimization as it can save up to 1.3 MB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-28%

Potential reduce by 85.3 kB

  • Original 302.0 kB
  • After minification 302.0 kB
  • After compression 216.8 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 85.3 kB or 28% of the original size.

CSS Optimization

-2%

Potential reduce by 2.3 kB

  • Original 124.9 kB
  • After minification 124.7 kB
  • After compression 122.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Lipstickempire.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 58 (79%)

Requests Now

73

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lipstick Empire. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lipstickempire.ca

lipstickempire.ca

76 ms

lipstickempire.ca

lipstickempire.ca

193 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

36 ms

formidableforms.css

formidableforms.css

76 ms

style.min.css

style.min.css

91 ms

style.min.css

style.min.css

89 ms

theme.min.css

theme.min.css

97 ms

style.basic.css

style.basic.css

99 ms

style-simple-red.css

style-simple-red.css

101 ms

elementor-icons.min.css

elementor-icons.min.css

103 ms

frontend-legacy.min.css

frontend-legacy.min.css

112 ms

frontend.min.css

frontend.min.css

137 ms

post-2382.css

post-2382.css

110 ms

frontend.min.css

frontend.min.css

147 ms

global.css

global.css

129 ms

post-2.css

post-2.css

133 ms

post-2383.css

post-2383.css

142 ms

post-2429.css

post-2429.css

144 ms

style.css

style.css

166 ms

ecs-style.css

ecs-style.css

164 ms

post-3379.css

post-3379.css

166 ms

css

css

59 ms

fontawesome.min.css

fontawesome.min.css

166 ms

solid.min.css

solid.min.css

171 ms

regular.min.css

regular.min.css

171 ms

brands.min.css

brands.min.css

178 ms

jquery.min.js

jquery.min.js

189 ms

jquery-migrate.min.js

jquery-migrate.min.js

207 ms

js

js

80 ms

ecs_ajax_pagination.js

ecs_ajax_pagination.js

205 ms

ecs.js

ecs.js

214 ms

css

css

64 ms

js

js

109 ms

sdk-v1.js

sdk-v1.js

44 ms

animations.min.css

animations.min.css

209 ms

dynamic-conditions-public.js

dynamic-conditions-public.js

310 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

311 ms

wp-polyfill.min.js

wp-polyfill.min.js

311 ms

hooks.min.js

hooks.min.js

311 ms

jquery.ajaxsearchlite.min.js

jquery.ajaxsearchlite.min.js

313 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

312 ms

imagesloaded.min.js

imagesloaded.min.js

314 ms

frm.min.js

frm.min.js

313 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

458 ms

webpack.runtime.min.js

webpack.runtime.min.js

408 ms

frontend-modules.min.js

frontend-modules.min.js

398 ms

frontend.min.js

frontend.min.js

397 ms

waypoints.min.js

waypoints.min.js

397 ms

core.min.js

core.min.js

392 ms

swiper.min.js

swiper.min.js

397 ms

share-link.min.js

share-link.min.js

393 ms

dialog.min.js

dialog.min.js

383 ms

frontend.min.js

frontend.min.js

385 ms

preloaded-elements-handlers.min.js

preloaded-elements-handlers.min.js

367 ms

preloaded-modules.min.js

preloaded-modules.min.js

368 ms

jquery.sticky.min.js

jquery.sticky.min.js

360 ms

gtm.js

gtm.js

273 ms

18b347de895aa444c24ca11d6.js

18b347de895aa444c24ca11d6.js

287 ms

LipstickEmpire_LOGO_BLK_GOLD_TRIM.png_142x65.webp

LipstickEmpire_LOGO_BLK_GOLD_TRIM.png_142x65.webp

242 ms

Lipstick-Empire-procedure.jpg

Lipstick-Empire-procedure.jpg

243 ms

DSC_6582-scaled.jpg

DSC_6582-scaled.jpg

519 ms

Screen-Shot-2022-04-10-at-3.11.17-PM.png

Screen-Shot-2022-04-10-at-3.11.17-PM.png

828 ms

October15_495-1-scaled.jpg

October15_495-1-scaled.jpg

316 ms

Brand-Mark-300x268.png

Brand-Mark-300x268.png

243 ms

LIPSTICKEMPIRE_BG_FLOWER_1.jpg

LIPSTICKEMPIRE_BG_FLOWER_1.jpg

247 ms

LIPSTICKEMPIRE_FOOTER_CONTACT2.jpg

LIPSTICKEMPIRE_FOOTER_CONTACT2.jpg

244 ms

LipstickEmpire_LOGO_W_750-300x138.png

LipstickEmpire_LOGO_W_750-300x138.png

246 ms

Best-in-edmonton-e1656890399788-300x292.png

Best-in-edmonton-e1656890399788-300x292.png

311 ms

analytics.js

analytics.js

91 ms

bodonixt-webfont.woff

bodonixt-webfont.woff

197 ms

fa-solid-900.woff

fa-solid-900.woff

199 ms

fa-regular-400.woff

fa-regular-400.woff

196 ms

fa-brands-400.woff

fa-brands-400.woff

198 ms

neue_einstellung_bold-webfont.woff

neue_einstellung_bold-webfont.woff

306 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrFivl6JABE.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrFivl6JABE.ttf

199 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEFvl6JABE.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEFvl6JABE.ttf

306 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEsvl6JABE.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEsvl6JABE.ttf

381 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrFbvl6JABE.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrFbvl6JABE.ttf

505 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrG3uV6JABE.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrG3uV6JABE.ttf

524 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrGFuV6JABE.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrGFuV6JABE.ttf

523 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrHbuV6JABE.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrHbuV6JABE.ttf

508 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEFuV6JABE.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrEFuV6JABE.ttf

521 ms

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrGFuF6JABE.ttf

l7gAbjR61M69yt8Z8w6FZf9WoBxdBrGFuF6JABE.ttf

503 ms

eicons.woff

eicons.woff

378 ms

eicons.woff

eicons.woff

373 ms

embed.js

embed.js

362 ms

maps

maps

474 ms

lipstickempire.ca

lipstickempire.ca

1098 ms

collect

collect

89 ms

picturefill.min.js

picturefill.min.js

184 ms

embed

embed

635 ms

js

js

35 ms

Accessibility Review

lipstickempire.ca accessibility score

95

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

lipstickempire.ca best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

lipstickempire.ca SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lipstickempire.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Lipstickempire.ca main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

lipstickempire.ca

Open Graph data is detected on the main page of Lipstick Empire. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: