Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

fakeart.net

David Hinnebusch Artworks

Page Load Speed

2.9 sec in total

First Response

317 ms

Resources Loaded

2.2 sec

Page Rendered

370 ms

fakeart.net screenshot

About Website

Click here to check amazing Fakeart content for United States. Otherwise, check out these important facts you probably never knew about fakeart.net

The online studio gallery & gift shop of David Hinnebusch, a Los Angeles based artist. He paints and mixes media in an expressionistic style.

Visit fakeart.net

Key Findings

We analyzed Fakeart.net page load time and found that the first response time was 317 ms and then it took 2.6 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

fakeart.net performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

19/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value19.2 s

0/100

10%

TBT (Total Blocking Time)

Value7,400 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value20.7 s

2/100

10%

Network Requests Diagram

fakeart.net

317 ms

shareaholic.js

6 ms

jquery.min.js

28 ms

sss.min.js

163 ms

sss.css

150 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 10% of them (11 requests) were addressed to the original Fakeart.net, 30% (33 requests) were made to Scontent.cdninstagram.com and 6% (7 requests) were made to Px.owneriq.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Fakeart.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (63%)

Content Size

1.7 MB

After Optimization

619.6 kB

In fact, the total size of Fakeart.net main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 191.4 kB

  • Original 210.7 kB
  • After minification 209.8 kB
  • After compression 19.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 191.4 kB or 91% of the original size.

Image Optimization

-7%

Potential reduce by 28.0 kB

  • Original 382.8 kB
  • After minification 354.9 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. Fakeart images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 774.0 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 233.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 774.0 kB or 77% of the original size.

CSS Optimization

-81%

Potential reduce by 52.4 kB

  • Original 64.7 kB
  • After minification 64.1 kB
  • After compression 12.3 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. Fakeart.net needs all CSS files to be minified and compressed as it can save up to 52.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (60%)

Requests Now

97

After Optimization

39

The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fakeart. 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 as a result speed up the page load time.

Accessibility Review

fakeart.net accessibility score

83

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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 IDs are not unique

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

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

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

fakeart.net 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fakeart.net SEO score

98

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fakeart.net 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 Fakeart.net main page’s claimed encoding is iso-8859-1. 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 Fakeart. 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: