Tools & Wizards About Us
pongcase.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

pongcase.com

Screen protectors and phone cases | Gadget Guard

Page Load Speed

2.8 sec in total

First Response

38 ms

Resources Loaded

1.5 sec

Page Rendered

1.3 sec

pongcase.com screenshot

About Website

Click here to check amazing Pongcase content for United States. Otherwise, check out these important facts you probably never knew about pongcase.com

gadget guard, gadget guard screen protectors, screen protectors, screen protection, alara, cellphone radiation

Visit pongcase.com

Key Findings

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

Performance Metrics

pongcase.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value7,130 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value33.7 s

0/100

10%

Network Requests Diagram

pongcase.com

38 ms

www.gadgetguard.com

52 ms

www.gadgetguard.com

79 ms

calendar.css

41 ms

styles-m.css

67 ms

Our browser made a total of 252 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Pongcase.com, 69% (174 requests) were made to Gadgetguard.com and 22% (56 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (601 ms) relates to the external source Gadgetguard.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 203.1 kB (9%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pongcase.com main page is 2.3 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. Only a small number of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 189.8 kB

  • Original 234.6 kB
  • After minification 213.8 kB
  • After compression 44.8 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 189.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.5 MB
  • After minification 1.5 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. Pongcase images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 13.0 kB

  • Original 420.7 kB
  • After minification 420.6 kB
  • After compression 407.7 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

-0%

Potential reduce by 261 B

  • Original 144.3 kB
  • After minification 144.2 kB
  • After compression 144.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. Pongcase.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 157 (83%)

Requests Now

189

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pongcase.com

pongcase.com

38 ms

www.gadgetguard.com

www.gadgetguard.com

52 ms

www.gadgetguard.com

www.gadgetguard.com

79 ms

calendar.css

calendar.css

41 ms

styles-m.css

styles-m.css

67 ms

owl.carousel.css

owl.carousel.css

45 ms

jquery.fancybox.css

jquery.fancybox.css

66 ms

bootstrap.min.css

bootstrap.min.css

55 ms

swiper.min.css

swiper.min.css

45 ms

amslick.min.css

amslick.min.css

93 ms

home.css

home.css

91 ms

styles-l.css

styles-l.css

92 ms

local.css

local.css

97 ms

require.js

require.js

97 ms

mixins.js

mixins.js

110 ms

requirejs-config.js

requirejs-config.js

114 ms

ird4hwr.css

ird4hwr.css

88 ms

nathan.css

nathan.css

111 ms

klaviyo.js

klaviyo.js

108 ms

font-awesome.min.css

font-awesome.min.css

110 ms

snippet.js

snippet.js

127 ms

vue.global.js

vue.global.js

125 ms

menu.js

menu.js

107 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

152 ms

p.css

p.css

57 ms

jquery.js

jquery.js

35 ms

common.js

common.js

24 ms

dataPost.js

dataPost.js

20 ms

bootstrap.js

bootstrap.js

25 ms

app.js

app.js

28 ms

form-key-provider.js

form-key-provider.js

24 ms

mage-translation-dictionary.js

mage-translation-dictionary.js

48 ms

theme.js

theme.js

45 ms

template.js

template.js

31 ms

confirm.js

confirm.js

117 ms

widget.js

widget.js

115 ms

jquery-mixin.js

jquery-mixin.js

114 ms

domReady.js

domReady.js

112 ms

main.js

main.js

278 ms

bootstrap.js

bootstrap.js

277 ms

gtm.js

gtm.js

366 ms

gtm.js

gtm.js

471 ms

bat.js

bat.js

304 ms

hotjar-2037696.js

hotjar-2037696.js

422 ms

gtm.js

gtm.js

469 ms

Gadget-Guard-Logo.png

Gadget-Guard-Logo.png

229 ms

icon-profile.svg

icon-profile.svg

228 ms

cart-icon.png

cart-icon.png

287 ms

protected-layout-desktop.jpg

protected-layout-desktop.jpg

286 ms

iphone-15-mode.png

iphone-15-mode.png

291 ms

iphone-15-pro-mode.png

iphone-15-pro-mode.png

234 ms

iphone-15-plus-mode.png

iphone-15-plus-mode.png

394 ms

iphone-15-pro-max-mode.png

iphone-15-pro-max-mode.png

398 ms

211122_LIQUID_packaging.png

211122_LIQUID_packaging.png

349 ms

211122_GLASS_PACKAGING.png

211122_GLASS_PACKAGING.png

394 ms

Artboard_103x.png

Artboard_103x.png

347 ms

MaskGroup192.png

MaskGroup192.png

398 ms

logo.png

logo.png

501 ms

404A17092.jpg

404A17092.jpg

505 ms

screen.png

screen.png

499 ms

stainless_steel_2_static__bh174dfhj9te_large.png

stainless_steel_2_static__bh174dfhj9te_large.png

500 ms

220801_Alara_iPhone13_sideways3.png

220801_Alara_iPhone13_sideways3.png

503 ms

5cb0633d80f2cf201a4c3253.png

5cb0633d80f2cf201a4c3253.png

499 ms

gg_alara_slim.png

gg_alara_slim.png

570 ms

404A20252.jpg

404A20252.jpg

573 ms

Liquid-Tech-icon2.png

Liquid-Tech-icon2.png

569 ms

ultrashock-tech-icon.png

ultrashock-tech-icon.png

570 ms

guardplus-backgound-people.jpg

guardplus-backgound-people.jpg

573 ms

Guard_Plus_Gif_Blk.gif

Guard_Plus_Gif_Blk.gif

581 ms

footer_logo-03.png

footer_logo-03.png

588 ms

logo-white_1.png

logo-white_1.png

595 ms

instagram-v32.png

instagram-v32.png

596 ms

youtube-black-v2.png

youtube-black-v2.png

586 ms

twitter-black-v2.png

twitter-black-v2.png

591 ms

facebook-black-v2.png

facebook-black-v2.png

601 ms

instagram-black-v2.png

instagram-black-v2.png

593 ms

types.js

types.js

594 ms

layout.js

layout.js

595 ms

autocomplete.js

autocomplete.js

600 ms

typeahead.js

typeahead.js

435 ms

opensans-400.woff

opensans-400.woff

533 ms

d

d

37 ms

d

d

111 ms

d

d

111 ms

d

d

110 ms

d

d

113 ms

d

d

58 ms

d

d

56 ms

d

d

172 ms

d

d

172 ms

d

d

173 ms

d

d

172 ms

d

d

170 ms

d

d

219 ms

d

d

325 ms

d

d

223 ms

d

d

326 ms

d

d

223 ms

d

d

221 ms

d

d

400 ms

d

d

223 ms

d

d

326 ms

d

d

325 ms

d

d

325 ms

d

d

329 ms

d

d

331 ms

d

d

330 ms

d

d

327 ms

d

d

329 ms

d

d

393 ms

d

d

390 ms

d

d

392 ms

d

d

392 ms

d

d

393 ms

d

d

406 ms

d

d

511 ms

d

d

400 ms

fender_analytics.113876fdc67592e7cbfd.js

fender_analytics.113876fdc67592e7cbfd.js

212 ms

static.047f24ade89e4aff54a9.js

static.047f24ade89e4aff54a9.js

213 ms

runtime.ca49fd11e57fd655c80b.js

runtime.ca49fd11e57fd655c80b.js

13 ms

sharedUtils.e8c90ec039ff40fd1c44.js

sharedUtils.e8c90ec039ff40fd1c44.js

102 ms

vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.b0930143925bb765e2d3.js

vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.b0930143925bb765e2d3.js

51 ms

vendors~signup_forms~post_identification_sync~onsite-triggering.98adbd4f3c00592d4b9b.js

vendors~signup_forms~post_identification_sync~onsite-triggering.98adbd4f3c00592d4b9b.js

49 ms

vendors~signup_forms.87a8144324ad4ca548d7.js

vendors~signup_forms.87a8144324ad4ca548d7.js

45 ms

default~signup_forms~onsite-triggering.88e27c46b11194aaa904.js

default~signup_forms~onsite-triggering.88e27c46b11194aaa904.js

45 ms

signup_forms.14aea6243661fa58c6fa.js

signup_forms.14aea6243661fa58c6fa.js

50 ms

d

d

356 ms

opensans-300.woff

opensans-300.woff

381 ms

opensans-600.woff

opensans-600.woff

466 ms

opensans-700.woff

opensans-700.woff

458 ms

d

d

344 ms

d

d

355 ms

26070026.js

26070026.js

225 ms

registry.js

registry.js

407 ms

d

d

299 ms

storage.js

storage.js

404 ms

d

d

305 ms

d

d

296 ms

quickcart.js

quickcart.js

404 ms

d

d

306 ms

weltpixel_ga4_persistentlayer.js

weltpixel_ga4_persistentlayer.js

348 ms

d

d

244 ms

d

d

247 ms

d

d

341 ms

weltpixel_ga4_gtm.js

weltpixel_ga4_gtm.js

350 ms

d

d

243 ms

modules.e4b2dc39f985f11fb1e4.js

modules.e4b2dc39f985f11fb1e4.js

188 ms

d

d

203 ms

customer-data.js

customer-data.js

303 ms

customer-data-mixin.js

customer-data-mixin.js

303 ms

d

d

204 ms

Blank-Theme-Icons.woff

Blank-Theme-Icons.woff

300 ms

text.js

text.js

299 ms

d

d

198 ms

d

d

205 ms

d

d

202 ms

d

d

104 ms

underscore.js

underscore.js

201 ms

translate.js

translate.js

202 ms

modal.js

modal.js

201 ms

wrapper.js

wrapper.js

200 ms

d

d

104 ms

d

d

104 ms

knockout.js

knockout.js

200 ms

knockout-es5.js

knockout-es5.js

197 ms

version.js

version.js

133 ms

engine.js

engine.js

135 ms

bootstrap.js

bootstrap.js

134 ms

observable_array.js

observable_array.js

130 ms

bound-nodes.js

bound-nodes.js

129 ms

scripts.js

scripts.js

123 ms

main.js

main.js

47 ms

amazon-pay-config.js

amazon-pay-config.js

43 ms

storage-wrapper.js

storage-wrapper.js

43 ms

local.js

local.js

42 ms

section-config.js

section-config.js

39 ms

url.js

url.js

40 ms

storage.js

storage.js

40 ms

js-translation.json

js-translation.json

77 ms

modal-popup.html

modal-popup.html

69 ms

modal-slide.html

modal-slide.html

75 ms

modal-custom.html

modal-custom.html

72 ms

key-codes.js

key-codes.js

32 ms

core.js

core.js

70 ms

z-index.js

z-index.js

69 ms

mage.js

mage.js

64 ms

knockout-repeat.js

knockout-repeat.js

52 ms

knockout-fast-foreach.js

knockout-fast-foreach.js

52 ms

events.js

events.js

51 ms

console-logger.js

console-logger.js

24 ms

renderer.js

renderer.js

30 ms

resizable.js

resizable.js

30 ms

i18n.js

i18n.js

30 ms

scope.js

scope.js

30 ms

range.js

range.js

31 ms

mage-init.js

mage-init.js

30 ms

keyboard.js

keyboard.js

44 ms

optgroup.js

optgroup.js

31 ms

after-render.js

after-render.js

62 ms

autoselect.js

autoselect.js

44 ms

datepicker.js

datepicker.js

45 ms

outer_click.js

outer_click.js

42 ms

fadeVisible.js

fadeVisible.js

45 ms

collapsible.js

collapsible.js

47 ms

staticChecked.js

staticChecked.js

48 ms

simple-checked.js

simple-checked.js

49 ms

bind-html.js

bind-html.js

47 ms

tooltip.js

tooltip.js

50 ms

color-picker.js

color-picker.js

57 ms

observable_source.js

observable_source.js

59 ms

js.storage.js

js.storage.js

57 ms

arrays.js

arrays.js

48 ms

compare.js

compare.js

48 ms

misc.js

misc.js

68 ms

objects.js

objects.js

57 ms

strings.js

strings.js

56 ms

template.js

template.js

70 ms

data.js

data.js

50 ms

disable-selection.js

disable-selection.js

52 ms

focusable.js

focusable.js

59 ms

form.js

form.js

73 ms

ie.js

ie.js

62 ms

keycode.js

keycode.js

62 ms

labels.js

labels.js

73 ms

jquery-patch.js

jquery-patch.js

71 ms

plugin.js

plugin.js

74 ms

safe-active-element.js

safe-active-element.js

77 ms

safe-blur.js

safe-blur.js

75 ms

scroll-parent.js

scroll-parent.js

83 ms

tabbable.js

tabbable.js

84 ms

unique-id.js

unique-id.js

85 ms

logger.js

logger.js

91 ms

entry-factory.js

entry-factory.js

89 ms

console-output-handler.js

console-output-handler.js

81 ms

formatter.js

formatter.js

88 ms

message-pool.js

message-pool.js

88 ms

levels-pool.js

levels-pool.js

89 ms

logger-utils.js

logger-utils.js

90 ms

async.js

async.js

96 ms

loader.js

loader.js

91 ms

tooltip.html

tooltip.html

97 ms

spectrum.js

spectrum.js

88 ms

tinycolor.js

tinycolor.js

85 ms

jquery.cookie.js

jquery.cookie.js

85 ms

class.js

class.js

90 ms

entry.js

entry.js

30 ms

moment.js

moment.js

41 ms

dom-observer.js

dom-observer.js

24 ms

bindings.js

bindings.js

21 ms

cookie-wrapper.js

cookie-wrapper.js

22 ms

js.cookie.js

js.cookie.js

18 ms

print.css

print.css

24 ms

Accessibility Review

pongcase.com accessibility score

91

Accessibility Issues

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

pongcase.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

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

pongcase.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Encoding

    UTF-8

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

pongcase.com

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