Tools & Wizards About Us
purecssapple.com screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    88% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

purecssapple.com

Pure CSS Apple Device Generator

Page Load Speed

2.5 sec in total

First Response

637 ms

Resources Loaded

1.6 sec

Page Rendered

206 ms

purecssapple.com screenshot

About Website

Visit purecssapple.com now to see the best up-to-date Pure CSS Apple content for United States and also check out these interesting facts you probably never knew about purecssapple.com

Create an Apple device with only CSS. No image, just code. iMac, Mac Book, iPad, iPhone version 4, 5 and 6 included.

Visit purecssapple.com

Key Findings

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

Performance Metrics

purecssapple.com performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

48/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

purecssapple.com

637 ms

master.css

352 ms

require-master.js

813 ms

logo3.svg

332 ms

imac.png

335 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 79% of them (19 requests) were addressed to the original Purecssapple.com, 13% (3 requests) were made to Themes.googleusercontent.com and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (975 ms) belongs to the original domain Purecssapple.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.5 kB (27%)

Content Size

204.7 kB

After Optimization

149.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Purecssapple.com main page is 204.7 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 123.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 23.5 kB

  • Original 27.9 kB
  • After minification 19.5 kB
  • After compression 4.4 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. This page needs HTML code to be minified as it can gain 8.4 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.5 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 11 B

  • Original 123.8 kB
  • After minification 123.8 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. Pure CSS Apple images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

purecssapple.com

purecssapple.com

637 ms

master.css

master.css

352 ms

require-master.js

require-master.js

813 ms

logo3.svg

logo3.svg

332 ms

imac.png

imac.png

335 ms

macbook.png

macbook.png

501 ms

ipad.png

ipad.png

347 ms

iphone4.png

iphone4.png

509 ms

iphone5.png

iphone5.png

505 ms

iphone6.png

iphone6.png

504 ms

1.jpg

1.jpg

507 ms

2.jpg

2.jpg

694 ms

3.jpg

3.jpg

686 ms

4.jpg

4.jpg

695 ms

5.jpg

5.jpg

689 ms

6.jpg

6.jpg

690 ms

6.jpg

6.jpg

846 ms

7.jpg

7.jpg

848 ms

5.jpg

5.jpg

975 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

41 ms

KT3KS9Aol4WfR6Vas8kNcg.woff

KT3KS9Aol4WfR6Vas8kNcg.woff

68 ms

wkfQbvfT_02e2IWO3yYueQ.woff

wkfQbvfT_02e2IWO3yYueQ.woff

72 ms

analytics.js

analytics.js

46 ms

collect

collect

24 ms

Accessibility Review

purecssapple.com accessibility score

71

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.

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

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

Form elements do not have associated labels

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

purecssapple.com best practices score

83

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

SEO Factors

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

robots.txt is not valid

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Purecssapple.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 Purecssapple.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

purecssapple.com

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