Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 65

    SEO

    Google-friendlier than
    25% of websites

somethingplay.com

썸띵플레이

Page Load Speed

31.3 sec in total

First Response

4.5 sec

Resources Loaded

22.4 sec

Page Rendered

4.3 sec

somethingplay.com screenshot

About Website

Visit somethingplay.com now to see the best up-to-date Somethingplay content and also check out these interesting facts you probably never knew about somethingplay.com

인테리어소품, 주방용품, 테이블웨어, 리빙편집샵, 소품샵, 썸띵플레이 | Outerwear, Tops, Dresses, Bottoms, Accessories

Visit somethingplay.com

Key Findings

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

Performance Metrics

somethingplay.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value55.1 s

0/100

25%

SI (Speed Index)

Value28.4 s

0/100

10%

TBT (Total Blocking Time)

Value2,050 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.471

18/100

15%

TTI (Time to Interactive)

Value36.3 s

0/100

10%

Network Requests Diagram

index

4519 ms

font.css

701 ms

common.css

459 ms

buttons.css

461 ms

jquery-ui-1.8.16.custom.css

700 ms

Our browser made a total of 345 requests to load all elements on the main page. We found that 96% of them (332 requests) were addressed to the original Somethingplay.com, 1% (4 requests) were made to F.vimeocdn.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Somethingplay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.9 MB (22%)

Content Size

13.1 MB

After Optimization

10.2 MB

In fact, the total size of Somethingplay.com main page is 13.1 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 10.8 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 1.3 MB

  • Original 1.4 MB
  • After minification 1.3 MB
  • After compression 159.6 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 1.3 MB or 89% of the original size.

Image Optimization

-9%

Potential reduce by 1.0 MB

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

JavaScript Optimization

-73%

Potential reduce by 484.4 kB

  • Original 661.2 kB
  • After minification 587.9 kB
  • After compression 176.8 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 484.4 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 125.7 kB

  • Original 147.3 kB
  • After minification 134.7 kB
  • After compression 21.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. Somethingplay.com needs all CSS files to be minified and compressed as it can save up to 125.7 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

343

After Optimization

293

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

Accessibility Review

somethingplay.com accessibility score

58

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Heading elements are not in a sequentially-descending order

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

Best Practices

somethingplay.com best practices score

50

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

somethingplay.com SEO score

65

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

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    KO

  • Language Claimed

    KO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Somethingplay.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Somethingplay.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

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