Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

prismagems.com

Prismagems - Projects from Rick Mace

Page Load Speed

323 ms in total

First Response

105 ms

Resources Loaded

217 ms

Page Rendered

1 ms

prismagems.com screenshot

About Website

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

Pages created by Rick Mace

Visit prismagems.com

Key Findings

We analyzed Prismagems.com page load time and found that the first response time was 105 ms and then it took 218 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

prismagems.com performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

prismagems.com

105 ms

element.js

33 ms

translateelement.css

67 ms

main.js

77 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 25% of them (1 request) were addressed to the original Prismagems.com, 50% (2 requests) were made to Translate.googleapis.com and 25% (1 request) were made to Translate.google.com. The less responsive or slowest element that took the longest time to load (105 ms) belongs to the original domain Prismagems.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 kB (15%)

Content Size

8.1 kB

After Optimization

6.9 kB

In fact, the total size of Prismagems.com main page is 8.1 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 3.6 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 1.0 kB

  • Original 1.8 kB
  • After minification 1.7 kB
  • After compression 736 B

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 1.0 kB or 58% of the original size.

JavaScript Optimization

-4%

Potential reduce by 119 B

  • Original 2.7 kB
  • After minification 2.7 kB
  • After compression 2.6 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

-2%

Potential reduce by 70 B

  • Original 3.6 kB
  • After minification 3.6 kB
  • After compression 3.5 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. Prismagems.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prismagems. According to our analytics all requests are already optimized.

Accessibility Review

prismagems.com accessibility score

96

Accessibility Issues

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

Best Practices

prismagems.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

prismagems.com SEO score

92

Search Engine Optimization Advices

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prismagems.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Prismagems.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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