Tools & Wizards About Us
smileycase.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

smileycase.com

Smiley Case - Hakiki Deri Telefon Kapakları- İphone Kılıfları - Telefon Kılıfları

Page Load Speed

12.6 sec in total

First Response

475 ms

Resources Loaded

6.2 sec

Page Rendered

5.9 sec

smileycase.com screenshot

About Website

Click here to check amazing Smiley Case content. Otherwise, check out these important facts you probably never knew about smileycase.com

Hakiki Deri Erkek - Bayan Telefon Kılıfları, ve aksesuar modelleri hakiki deri malzemelerle tasarlayan Smiley Case tarafından beğeninize sunuluyor.

Visit smileycase.com

Key Findings

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

Performance Metrics

smileycase.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.715

7/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

smileycase.com

475 ms

smileycase.com

517 ms

www.smileycase.com

1671 ms

font-awesome.min.css

283 ms

line-awesome.min.css

554 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 87% of them (46 requests) were addressed to the original Smileycase.com, 4% (2 requests) were made to Cdn.jsdelivr.net and 4% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Smileycase.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 455.0 kB (12%)

Content Size

3.8 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Smileycase.com main page is 3.8 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. 65% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 154.0 kB

  • Original 166.8 kB
  • After minification 140.1 kB
  • After compression 12.9 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 26.8 kB, which is 16% 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 154.0 kB or 92% of the original size.

Image Optimization

-8%

Potential reduce by 286.1 kB

  • Original 3.5 MB
  • After minification 3.2 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. Smiley Case images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 6.7 kB

  • Original 71.1 kB
  • After minification 71.1 kB
  • After compression 64.4 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

-7%

Potential reduce by 8.1 kB

  • Original 109.9 kB
  • After minification 109.9 kB
  • After compression 101.7 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. Smileycase.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (72%)

Requests Now

46

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

smileycase.com

smileycase.com

475 ms

smileycase.com

smileycase.com

517 ms

www.smileycase.com

www.smileycase.com

1671 ms

font-awesome.min.css

font-awesome.min.css

283 ms

line-awesome.min.css

line-awesome.min.css

554 ms

style.css

style.css

653 ms

responsive.css

responsive.css

435 ms

bootstrap.min.css

bootstrap.min.css

458 ms

site_style.css

site_style.css

548 ms

jquery-ui.css

jquery-ui.css

550 ms

swiper.min.css

swiper.min.css

650 ms

flag-icon.css

flag-icon.css

685 ms

jquery.min.js

jquery.min.js

763 ms

custom.js

custom.js

687 ms

cookieconsent.min.css

cookieconsent.min.css

52 ms

cookieconsent.min.js

cookieconsent.min.js

56 ms

aos.css

aos.css

682 ms

modules_style.css

modules_style.css

717 ms

jquery.fancybox.css

jquery.fancybox.css

687 ms

jquery.fancybox.js

jquery.fancybox.js

723 ms

jquery_cook_new.js

jquery_cook_new.js

804 ms

swiper-bundle.min.js

swiper-bundle.min.js

195 ms

aos.js

aos.js

685 ms

js

js

238 ms

1_9_7_jquery.lazyload.js

1_9_7_jquery.lazyload.js

710 ms

popper.min.js

popper.min.js

739 ms

bootstrap.min.js

bootstrap.min.js

755 ms

common.min.js

common.min.js

778 ms

jquery.appear.min.js

jquery.appear.min.js

806 ms

theme.js

theme.js

842 ms

theme.init.js

theme.init.js

843 ms

jquery-ui.min.js

jquery-ui.min.js

190 ms

footerlibs.js

footerlibs.js

868 ms

mobile.css

mobile.css

589 ms

1152x864.css

1152x864.css

615 ms

1280x1024.css

1280x1024.css

622 ms

88481-600-SMiLEYCASE_POPUP.png

88481-600-SMiLEYCASE_POPUP.png

577 ms

87130-111-smileycase-logo-black.png

87130-111-smileycase-logo-black.png

157 ms

slider_marvel-slider62455698984181.png

slider_marvel-slider62455698984181.png

1117 ms

slider_toon-case-slider-262284656139735.png

slider_toon-case-slider-262284656139735.png

1017 ms

slider_slider-red52228581607368.png

slider_slider-red52228581607368.png

722 ms

load.gif

load.gif

531 ms

18850-140-smileycase-logo-black.png

18850-140-smileycase-logo-black.png

297 ms

Pp-info_1.png

Pp-info_1.png

408 ms

95714-419-40173-427-13249-450-2324670968738-46-card.png

95714-419-40173-427-13249-450-2324670968738-46-card.png

721 ms

fbevents.js

fbevents.js

95 ms

tr.svg

tr.svg

311 ms

365545398910333

365545398910333

508 ms

8751-993-48266-197-bac.png

8751-993-48266-197-bac.png

361 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

921 ms

ionicons.ttf

ionicons.ttf

342 ms

la-solid-900.woff

la-solid-900.woff

150 ms

la-regular-400.woff

la-regular-400.woff

342 ms

Accessibility Review

smileycase.com accessibility score

75

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

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

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.

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

smileycase.com 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

smileycase.com SEO score

80

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    TR

  • Language Claimed

    TR

  • Encoding

    UTF-8

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

smileycase.com

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