Tools & Wizards About Us
glitterly.app screenshot

Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

glitterly.app

Glitterly - Image and video generation tools and API

Page Load Speed

1.3 sec in total

First Response

80 ms

Resources Loaded

671 ms

Page Rendered

560 ms

glitterly.app screenshot

About Website

Welcome to glitterly.app homepage info - get ready to check Glitterly best content right away, or after learning these important things about glitterly.app

Simple image and video tools and API to help you automatically create beautiful graphics for social media, banners, ecommerce, or publishing.

Visit glitterly.app

Key Findings

We analyzed Glitterly.app page load time and found that the first response time was 80 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

glitterly.app performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.313

37/100

15%

TTI (Time to Interactive)

Value2.1 s

99/100

10%

Network Requests Diagram

glitterly.app

80 ms

glitterly.app

287 ms

5e73a9a81739bc572a91.css

52 ms

dd.png

23 ms

create_open_graph_image_from_url_api_sbd2gn.jpg

307 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 68% of them (15 requests) were addressed to the original Glitterly.app, 32% (7 requests) were made to Res.cloudinary.com. The less responsive or slowest element that took the longest time to load (307 ms) relates to the external source Res.cloudinary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.2 kB (6%)

Content Size

594.8 kB

After Optimization

557.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Glitterly.app main page is 594.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 430.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 32.8 kB

  • Original 42.8 kB
  • After minification 42.7 kB
  • After compression 10.0 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 32.8 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 4.1 kB

  • Original 430.4 kB
  • After minification 426.3 kB

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. Glitterly images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 286 B

  • Original 116.4 kB
  • After minification 116.4 kB
  • After compression 116.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 34 B

  • Original 5.2 kB
  • After minification 5.2 kB
  • After compression 5.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. Glitterly.app has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (50%)

Requests Now

20

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

glitterly.app

glitterly.app

80 ms

glitterly.app

glitterly.app

287 ms

5e73a9a81739bc572a91.css

5e73a9a81739bc572a91.css

52 ms

dd.png

dd.png

23 ms

create_open_graph_image_from_url_api_sbd2gn.jpg

create_open_graph_image_from_url_api_sbd2gn.jpg

307 ms

email-decode.min.js

email-decode.min.js

24 ms

polyfills-52c5b5af9b38d4a18d68.js

polyfills-52c5b5af9b38d4a18d68.js

33 ms

webpack-8cc25addf11472ea3c78.js

webpack-8cc25addf11472ea3c78.js

70 ms

framework.ce4a96022bc463719e4f.js

framework.ce4a96022bc463719e4f.js

163 ms

1c7a7ce126b8f73f23b18af154442c8e5e3839c4.b1ad4c942db2aff27052.js

1c7a7ce126b8f73f23b18af154442c8e5e3839c4.b1ad4c942db2aff27052.js

34 ms

a7791d51b7363fccdf3b08761c502222d76ce52c.264cba1beeb6566f9c23.js

a7791d51b7363fccdf3b08761c502222d76ce52c.264cba1beeb6566f9c23.js

83 ms

main-f55e015c27336c17ca60.js

main-f55e015c27336c17ca60.js

87 ms

_app-e0a063ebbc67a48b772b.js

_app-e0a063ebbc67a48b772b.js

43 ms

index-9f745b224d0fe6db4c6f.js

index-9f745b224d0fe6db4c6f.js

58 ms

_buildManifest.js

_buildManifest.js

100 ms

_ssgManifest.js

_ssgManifest.js

62 ms

automated_og_image_api_hrfwxe.jpg

automated_og_image_api_hrfwxe.jpg

180 ms

automate_user_generated_content_ccrcbf.jpg

automate_user_generated_content_ccrcbf.jpg

185 ms

automate_marketing_banner_lfnkmg.jpg

automate_marketing_banner_lfnkmg.jpg

180 ms

1620925466230_fsoatv.jpg

1620925466230_fsoatv.jpg

205 ms

oxqiauj44gsscmpobi8n.jpg

oxqiauj44gsscmpobi8n.jpg

212 ms

PhotoRoom_api_jwldnj.jpeg

PhotoRoom_api_jwldnj.jpeg

186 ms

Accessibility Review

glitterly.app accessibility score

92

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.

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

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

glitterly.app best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

glitterly.app SEO score

85

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Glitterly.app 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 Glitterly.app 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

glitterly.app

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