Tools & Wizards About Us
makenzierae.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

Page Load Speed

919 ms in total

First Response

149 ms

Resources Loaded

654 ms

Page Rendered

116 ms

makenzierae.com screenshot

About Website

Click here to check amazing Makenzierae content. Otherwise, check out these important facts you probably never knew about makenzierae.com

Visit makenzierae.com

Key Findings

We analyzed Makenzierae.com page load time and found that the first response time was 149 ms and then it took 770 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

makenzierae.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.138

79/100

15%

TTI (Time to Interactive)

Value34.4 s

0/100

10%

Network Requests Diagram

makenzierae.com

149 ms

www.makenzierae.com

80 ms

bt

87 ms

require.min.js

56 ms

main-r.min.js

59 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Makenzierae.com, 75% (27 requests) were made to Static.parastorage.com and 11% (4 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (153 ms) relates to the external source Static.parastorage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (77%)

Content Size

2.5 MB

After Optimization

596.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Makenzierae.com main page is 2.5 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. 70% of websites need less resources to load. Javascripts take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 22.7 kB

  • Original 29.3 kB
  • After minification 29.0 kB
  • After compression 6.6 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 22.7 kB or 78% of the original size.

JavaScript Optimization

-77%

Potential reduce by 1.9 MB

  • Original 2.5 MB
  • After minification 2.5 MB
  • After compression 588.4 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 1.9 MB or 77% of the original size.

CSS Optimization

-77%

Potential reduce by 5.8 kB

  • Original 7.5 kB
  • After minification 6.0 kB
  • After compression 1.7 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. Makenzierae.com needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (74%)

Requests Now

34

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

makenzierae.com

makenzierae.com

149 ms

www.makenzierae.com

www.makenzierae.com

80 ms

bt

bt

87 ms

require.min.js

require.min.js

56 ms

main-r.min.js

main-r.min.js

59 ms

viewer.css

viewer.css

97 ms

dynamicmodel

dynamicmodel

6 ms

cd63b4_efb71c5f83060e2e925bf475124a8cb0_249.json.z

cd63b4_efb71c5f83060e2e925bf475124a8cb0_249.json.z

94 ms

cd63b4_0fc4f8628443776e5e1d92f8e4f56353_249.json.z

cd63b4_0fc4f8628443776e5e1d92f8e4f56353_249.json.z

97 ms

ugc-viewer

ugc-viewer

38 ms

ugc-viewer

ugc-viewer

96 ms

bt

bt

94 ms

skins.min.js

skins.min.js

153 ms

components.min.js

components.min.js

151 ms

utils.min.js

utils.min.js

150 ms

core.min.js

core.min.js

92 ms

react-with-addons.min.js

react-with-addons.min.js

92 ms

lodash.min.js

lodash.min.js

38 ms

TweenMax.min.js

TweenMax.min.js

54 ms

layout.min.js

layout.min.js

147 ms

tpa.min.js

tpa.min.js

147 ms

fonts.min.js

fonts.min.js

145 ms

animations.min.js

animations.min.js

148 ms

swfobject.min.js

swfobject.min.js

153 ms

mousetrap.min.js

mousetrap.min.js

150 ms

tweenEngine.min.js

tweenEngine.min.js

151 ms

DrawSVGPlugin.min.js

DrawSVGPlugin.min.js

147 ms

react-dom.min.js

react-dom.min.js

147 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

147 ms

widgets.min.js

widgets.min.js

148 ms

experiment.js

experiment.js

149 ms

render.min.js

render.min.js

149 ms

wixappsCore.min.js

wixappsCore.min.js

151 ms

wixappsBuilder.min.js

wixappsBuilder.min.js

149 ms

zepto.min.js

zepto.min.js

147 ms

color.min.js

color.min.js

146 ms

Accessibility Review

makenzierae.com accessibility score

55

Accessibility Issues

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

makenzierae.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

makenzierae.com SEO score

82

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

Image elements do not have [alt] attributes

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Makenzierae.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Makenzierae.com 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

makenzierae.com

Open Graph description is not detected on the main page of Makenzierae. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: