Tools & Wizards About Us
alexis.com screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

alexis.com

ALEXIS

Page Load Speed

2.5 sec in total

First Response

135 ms

Resources Loaded

1.7 sec

Page Rendered

683 ms

alexis.com screenshot

About Website

Click here to check amazing ALEXIS content for United States. Otherwise, check out these important facts you probably never knew about alexis.com

Freedom reborn & better than ever! The USA Freedom Kids patriotic songs will melt your heart and lift your spirit. Come celebrate freedom with the USA Freedom Kids!

Visit alexis.com

Key Findings

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

Performance Metrics

alexis.com performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

www.usafreedomkids.com

135 ms

css

50 ms

css

63 ms

site.css

15 ms

duel.js

35 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Alexis.com, 35% (20 requests) were made to Nebula.wsimg.com and 14% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Nebula.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.7 kB (4%)

Content Size

9.2 MB

After Optimization

8.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Alexis.com main page is 9.2 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. 65% of websites need less resources to load. Images take 8.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 37.8 kB

  • Original 46.0 kB
  • After minification 46.0 kB
  • After compression 8.2 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 37.8 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 72.3 kB

  • Original 8.8 MB
  • After minification 8.8 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. ALEXIS images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 183.4 kB

  • Original 311.4 kB
  • After minification 311.0 kB
  • After compression 128.0 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 183.4 kB or 59% of the original size.

CSS Optimization

-57%

Potential reduce by 30.1 kB

  • Original 53.0 kB
  • After minification 53.0 kB
  • After compression 22.9 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. Alexis.com needs all CSS files to be minified and compressed as it can save up to 30.1 kB or 57% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.usafreedomkids.com

www.usafreedomkids.com

135 ms

css

css

50 ms

css

css

63 ms

site.css

site.css

15 ms

duel.js

duel.js

35 ms

jq.js

jq.js

29 ms

1d6c21f069dbf44f8a3f2ecb71207cae

1d6c21f069dbf44f8a3f2ecb71207cae

353 ms

media.lightbox.js

media.lightbox.js

24 ms

customForm.published.js

customForm.published.js

59 ms

cookiemanager.js

cookiemanager.js

26 ms

iebackground.js

iebackground.js

52 ms

analytics.js

analytics.js

67 ms

d370657c831cbdfc1b4f468e48c5e64c

d370657c831cbdfc1b4f468e48c5e64c

60 ms

f076650a761512fefc97d448ba93172f

f076650a761512fefc97d448ba93172f

122 ms

5ad548ce9bf52749eb3203f5cf0ca6ba

5ad548ce9bf52749eb3203f5cf0ca6ba

67 ms

a9b1f02224b6b875e75c4991427ab9f4

a9b1f02224b6b875e75c4991427ab9f4

121 ms

e4c8f77e2dc58799355e2d3027919631

e4c8f77e2dc58799355e2d3027919631

58 ms

2140806c9690c6aa8746af7d05136056

2140806c9690c6aa8746af7d05136056

1225 ms

b8715525544692bcbbc338f6946f47a0

b8715525544692bcbbc338f6946f47a0

170 ms

12b623f3fabae9fe96d2007fa2e562eb

12b623f3fabae9fe96d2007fa2e562eb

143 ms

b97b67377d7272cb09ebe46655353bc1

b97b67377d7272cb09ebe46655353bc1

149 ms

ed53f6e3fac0fd3882a361408bb777cc

ed53f6e3fac0fd3882a361408bb777cc

145 ms

5f15b4960f6c2f1efc19b5ddca689493

5f15b4960f6c2f1efc19b5ddca689493

160 ms

39301140b351ea4e688a0a0ae719a44d

39301140b351ea4e688a0a0ae719a44d

160 ms

8afbb68a79ce0f922edabf573795a123

8afbb68a79ce0f922edabf573795a123

168 ms

225ac64ea9a2df74c034ba4edf45b570

225ac64ea9a2df74c034ba4edf45b570

200 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

62 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

119 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

130 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

142 ms

util.instances.js

util.instances.js

39 ms

util.model.js

util.model.js

46 ms

documentHelper.js

documentHelper.js

42 ms

fancybox.js

fancybox.js

110 ms

util.window.js

util.window.js

44 ms

regexhelper.js

regexhelper.js

16 ms

api.guid.js

api.guid.js

79 ms

jquery.xDomainRequest.js

jquery.xDomainRequest.js

81 ms

tipper.js

tipper.js

81 ms

datepicker.js

datepicker.js

80 ms

jquery.watermark.js

jquery.watermark.js

80 ms

collect

collect

32 ms

qx1LSqts-NtiKcLw4N03IC5FJMZltoAAwO2fP7iHu2o.ttf

qx1LSqts-NtiKcLw4N03IC5FJMZltoAAwO2fP7iHu2o.ttf

53 ms

L74890HNVnUypqWjqGUt1aCWcynf_cDxXwCLxiixG1c.ttf

L74890HNVnUypqWjqGUt1aCWcynf_cDxXwCLxiixG1c.ttf

27 ms

Hm1qjDlZpOdVXoa-QGE7_w.ttf

Hm1qjDlZpOdVXoa-QGE7_w.ttf

36 ms

LzkxWS-af0Br2Sk_YgSJY6XrD0ew9-Ooe_pdZm-U6E0.ttf

LzkxWS-af0Br2Sk_YgSJY6XrD0ew9-Ooe_pdZm-U6E0.ttf

47 ms

sf.tipper.js

sf.tipper.js

26 ms

fancybox.css

fancybox.css

31 ms

sf.datepicker.js

sf.datepicker.js

22 ms

sf.core.pkg.js

sf.core.pkg.js

9 ms

app.css

app.css

57 ms

app.css

app.css

49 ms

19b260f36b3c39cfdba5d03b44e7f2cc

19b260f36b3c39cfdba5d03b44e7f2cc

200 ms

c62df4ef205626464d72ef7fb4213693

c62df4ef205626464d72ef7fb4213693

107 ms

7e0f7250e1cba707a7809804c5ed1ad7

7e0f7250e1cba707a7809804c5ed1ad7

68 ms

a61137cd8ef7b36fbd5a407333f89640

a61137cd8ef7b36fbd5a407333f89640

162 ms

fa411f8a4da044e86a601a773cc22c38

fa411f8a4da044e86a601a773cc22c38

184 ms

Accessibility Review

alexis.com accessibility score

86

Accessibility Issues

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

alexis.com best practices score

92

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

Page has valid source maps

SEO Factors

alexis.com SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

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 Alexis.com 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 Alexis.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

alexis.com

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