Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

spigen.ph

Spigen Philippines | Phone Cases, Phone Car Mounts, Phone Accessories

Page Load Speed

8.1 sec in total

First Response

792 ms

Resources Loaded

7 sec

Page Rendered

274 ms

spigen.ph screenshot

About Website

Welcome to spigen.ph homepage info - get ready to check Spigen best content for Philippines right away, or after learning these important things about spigen.ph

At Spigen Philippines, we are built on creating protective phone cases and accessories that push the boundaries of design, technology, and availability.

Visit spigen.ph

Key Findings

We analyzed Spigen.ph page load time and found that the first response time was 792 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

spigen.ph performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value42.9 s

0/100

25%

SI (Speed Index)

Value24.5 s

0/100

10%

TBT (Total Blocking Time)

Value4,240 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value29.2 s

0/100

10%

Network Requests Diagram

spigen.ph

792 ms

spigen.ph

2194 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

285 ms

css__LeQxW73LSYscb1O__H6f-j_jdAzhZBaesGL19KEB6U.css

511 ms

css_vfQj5y4dgy-7Nzmrmdw-g4PrVZj1Vt4ZruqU9IqLIHo.css

730 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 78% of them (42 requests) were addressed to the original Spigen.ph, 7% (4 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Spigen.ph.

Page Optimization Overview & Recommendations

Page size can be reduced by 983.7 kB (13%)

Content Size

7.6 MB

After Optimization

6.7 MB

In fact, the total size of Spigen.ph main page is 7.6 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. 45% of websites need less resources to load. Images take 7.5 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 51.0 kB

  • Original 62.5 kB
  • After minification 60.6 kB
  • After compression 11.5 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 51.0 kB or 82% of the original size.

Image Optimization

-12%

Potential reduce by 915.4 kB

  • Original 7.5 MB
  • After minification 6.6 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. Obviously, Spigen needs image optimization as it can save up to 915.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 17.0 kB

  • Original 84.0 kB
  • After minification 83.3 kB
  • After compression 67.0 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 17.0 kB or 20% of the original size.

CSS Optimization

-1%

Potential reduce by 221 B

  • Original 22.3 kB
  • After minification 22.3 kB
  • After compression 22.0 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. Spigen.ph has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (45%)

Requests Now

47

After Optimization

26

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

Accessibility Review

spigen.ph accessibility score

87

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 input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

spigen.ph best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

spigen.ph SEO score

83

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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