Tools & Wizards About Us
foilrose.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

foilrose.com

James Anderson | Senior UI/UX Designer & Branding Specialist in Utah

Page Load Speed

2.7 sec in total

First Response

203 ms

Resources Loaded

1.8 sec

Page Rendered

722 ms

foilrose.com screenshot

About Website

Welcome to foilrose.com homepage info - get ready to check Foilrose best content right away, or after learning these important things about foilrose.com

Explore the digital portfolio of James Anderson, a Senior UI/UX Designer in Utah. Specializing in product design, branding, and web design for startups and global brands.

Visit foilrose.com

Key Findings

We analyzed Foilrose.com page load time and found that the first response time was 203 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

foilrose.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

foilrose.com

203 ms

foilrose.com

248 ms

jamesandersonstudios.com

288 ms

css

36 ms

aos.css

66 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Foilrose.com, 61% (38 requests) were made to Jamesandersonstudios.com and 29% (18 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (969 ms) relates to the external source Jamesandersonstudios.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 337.4 kB (3%)

Content Size

11.3 MB

After Optimization

10.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foilrose.com main page is 11.3 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 10.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 58.4 kB

  • Original 70.9 kB
  • After minification 63.9 kB
  • After compression 12.5 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 58.4 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 212.2 kB

  • Original 10.8 MB
  • After minification 10.6 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. Foilrose images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 44.8 kB

  • Original 249.1 kB
  • After minification 249.1 kB
  • After compression 204.2 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 44.8 kB or 18% of the original size.

CSS Optimization

-24%

Potential reduce by 22.0 kB

  • Original 91.2 kB
  • After minification 91.2 kB
  • After compression 69.2 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. Foilrose.com needs all CSS files to be minified and compressed as it can save up to 22.0 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (49%)

Requests Now

39

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

foilrose.com

foilrose.com

203 ms

foilrose.com

foilrose.com

248 ms

jamesandersonstudios.com

jamesandersonstudios.com

288 ms

css

css

36 ms

aos.css

aos.css

66 ms

bootstrap.min.css

bootstrap.min.css

193 ms

bootstrap-icons.css

bootstrap-icons.css

248 ms

boxicons.min.css

boxicons.min.css

233 ms

glightbox.min.css

glightbox.min.css

183 ms

swiper-bundle.min.css

swiper-bundle.min.css

187 ms

style.css

style.css

184 ms

JA-Logo-Reversed.png

JA-Logo-Reversed.png

470 ms

Me-V3.png

Me-V3.png

842 ms

seamless.js

seamless.js

39 ms

purecounter_vanilla.js

purecounter_vanilla.js

467 ms

aos.js

aos.js

467 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

469 ms

glightbox.min.js

glightbox.min.js

468 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

469 ms

swiper-bundle.min.js

swiper-bundle.min.js

524 ms

typed.umd.js

typed.umd.js

469 ms

noframework.waypoints.js

noframework.waypoints.js

470 ms

validate.js

validate.js

470 ms

main.js

main.js

480 ms

Deluxe_Digital_Website_1.png

Deluxe_Digital_Website_1.png

664 ms

MandoCreator_Website.png

MandoCreator_Website.png

672 ms

Ducworks_Illustration.png

Ducworks_Illustration.png

674 ms

Mayhew_Logo.png

Mayhew_Logo.png

600 ms

Veggie_Illustration.png

Veggie_Illustration.png

787 ms

BearFire_Forge_Logo.png

BearFire_Forge_Logo.png

768 ms

Church_Website-5.png

Church_Website-5.png

727 ms

Gladiator_Fightwear_Logo-1.png

Gladiator_Fightwear_Logo-1.png

785 ms

Loch_Salann_Website.png

Loch_Salann_Website.png

787 ms

Cliff_England_Comics.png

Cliff_England_Comics.png

854 ms

Jaguar_AI_Logo.png

Jaguar_AI_Logo.png

830 ms

SilverCare_Mobile.png

SilverCare_Mobile.png

850 ms

MyCore_Mobile.png

MyCore_Mobile.png

899 ms

CST_Logo.png

CST_Logo.png

848 ms

Fish_Illustration.png

Fish_Illustration.png

969 ms

banner.jpg

banner.jpg

551 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

27 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff

51 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff

52 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

53 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff

53 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

49 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

51 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

54 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

53 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

55 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

55 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

55 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

55 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

56 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff

59 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexg.woff

56 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexg.woff

58 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexg.woff

59 ms

bootstrap-icons.woff

bootstrap-icons.woff

462 ms

boxicons.woff

boxicons.woff

438 ms

31.2144e3e3b53491c6caa4.js

31.2144e3e3b53491c6caa4.js

60 ms

205.d3bfeda278365868fbb5.js

205.d3bfeda278365868fbb5.js

72 ms

Accessibility Review

foilrose.com 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 progressbar elements do not have accessible names.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

foilrose.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

foilrose.com SEO score

100

Search Engine Optimization Advices

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 Foilrose.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 Foilrose.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

foilrose.com

Open Graph description is not detected on the main page of Foilrose. 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: