Tools & Wizards About Us
twincitiespawn.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

twincitiespawn.com

Twin Cities Pawn – Got Gold? We Pay Cash

Page Load Speed

10.9 sec in total

First Response

4 sec

Resources Loaded

6.3 sec

Page Rendered

546 ms

twincitiespawn.com screenshot

About Website

Welcome to twincitiespawn.com homepage info - get ready to check Twin Cities Pawn best content right away, or after learning these important things about twincitiespawn.com

Visit twincitiespawn.com

Key Findings

We analyzed Twincitiespawn.com page load time and found that the first response time was 4 sec and then it took 6.9 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

twincitiespawn.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value1,370 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

twincitiespawn.com

3975 ms

blocks.css

133 ms

czicons.css

130 ms

styles.css

413 ms

woocommerce-layout.css

127 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 82% of them (98 requests) were addressed to the original Twincitiespawn.com, 8% (9 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Twincitiespawn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 435.9 kB (26%)

Content Size

1.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Twincitiespawn.com main page is 1.7 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. 80% 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. Javascripts take 751.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 121.2 kB

  • Original 149.5 kB
  • After minification 147.1 kB
  • After compression 28.3 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 121.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 1.4 kB

  • Original 424.8 kB
  • After minification 423.4 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. Twin Cities Pawn images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 233.5 kB

  • Original 751.7 kB
  • After minification 751.5 kB
  • After compression 518.1 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 233.5 kB or 31% of the original size.

CSS Optimization

-21%

Potential reduce by 79.8 kB

  • Original 378.8 kB
  • After minification 378.5 kB
  • After compression 298.9 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. Twincitiespawn.com needs all CSS files to be minified and compressed as it can save up to 79.8 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 89 (89%)

Requests Now

100

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

twincitiespawn.com

twincitiespawn.com

3975 ms

blocks.css

blocks.css

133 ms

czicons.css

czicons.css

130 ms

styles.css

styles.css

413 ms

woocommerce-layout.css

woocommerce-layout.css

127 ms

woocommerce.css

woocommerce.css

187 ms

fontawesome.css

fontawesome.css

296 ms

review_widget_form.css

review_widget_form.css

193 ms

review_widget_display.css

review_widget_display.css

195 ms

core.css

core.css

262 ms

fixed_side.css

fixed_side.css

252 ms

css

css

43 ms

woocommerce.css

woocommerce.css

259 ms

share.css

share.css

258 ms

mobile-nav.css

mobile-nav.css

333 ms

codevzplus.css

codevzplus.css

334 ms

frontend-lite.min.css

frontend-lite.min.css

381 ms

general.min.css

general.min.css

330 ms

eael-2181.css

eael-2181.css

251 ms

elementor-icons.min.css

elementor-icons.min.css

358 ms

swiper.min.css

swiper.min.css

400 ms

post-1626.css

post-1626.css

394 ms

frontend-lite.min.css

frontend-lite.min.css

397 ms

global.css

global.css

431 ms

post-2181.css

post-2181.css

442 ms

elementor.css

elementor.css

457 ms

v4-shims.min.css

v4-shims.min.css

465 ms

all.min.css

all.min.css

470 ms

css

css

38 ms

jquery.min.js

jquery.min.js

529 ms

jquery-migrate.min.js

jquery-migrate.min.js

497 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

503 ms

add-to-cart.min.js

add-to-cart.min.js

519 ms

js.cookie.min.js

js.cookie.min.js

525 ms

woocommerce.min.js

woocommerce.min.js

611 ms

cart-fragments.min.js

cart-fragments.min.js

616 ms

wc-blocks.css

wc-blocks.css

571 ms

dashicons.min.css

dashicons.min.css

636 ms

display-opinions-light.css

display-opinions-light.css

515 ms

font-awesome.min.css

font-awesome.min.css

499 ms

rs6.css

rs6.css

496 ms

photoswipe.min.css

photoswipe.min.css

508 ms

default-skin.min.css

default-skin.min.css

465 ms

css

css

19 ms

css

css

39 ms

hooks.min.js

hooks.min.js

517 ms

css

css

18 ms

i18n.min.js

i18n.min.js

515 ms

index.js

index.js

454 ms

index.js

index.js

469 ms

rbtools.min.js

rbtools.min.js

527 ms

rs6.min.js

rs6.min.js

604 ms

review_widget_form.js

review_widget_form.js

493 ms

codevz-menu.min.js

codevz-menu.min.js

455 ms

custom.js

custom.js

452 ms

woocommerce.js

woocommerce.js

473 ms

codevzplus.js

codevzplus.js

488 ms

share.js

share.js

468 ms

mobile-nav.js

mobile-nav.js

440 ms

sourcebuster.min.js

sourcebuster.min.js

450 ms

order-attribution.min.js

order-attribution.min.js

454 ms

general.min.js

general.min.js

492 ms

eael-2181.js

eael-2181.js

91 ms

underscore.min.js

underscore.min.js

452 ms

backbone.min.js

backbone.min.js

459 ms

front-end-deps.js

front-end-deps.js

456 ms

front-end.js

front-end.js

458 ms

elementor.js

elementor.js

439 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

456 ms

webpack.runtime.min.js

webpack.runtime.min.js

456 ms

frontend-modules.min.js

frontend-modules.min.js

508 ms

frontend.min.js

frontend.min.js

461 ms

waypoints.min.js

waypoints.min.js

463 ms

core.min.js

core.min.js

387 ms

frontend.min.js

frontend.min.js

409 ms

preloaded-elements-handlers.min.js

preloaded-elements-handlers.min.js

472 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

427 ms

photoswipe.min.js

photoswipe.min.js

439 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

442 ms

wp-util.min.js

wp-util.min.js

454 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

85 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

103 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

124 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

123 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

134 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

134 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

135 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

135 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

136 ms

embed

embed

254 ms

embed

embed

254 ms

embed

embed

346 ms

embed

embed

319 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

436 ms

single-product.min.js

single-product.min.js

460 ms

fa-solid-900.ttf

fa-solid-900.ttf

688 ms

fa-regular-400.ttf

fa-regular-400.ttf

683 ms

czicons.woff

czicons.woff

684 ms

fa-brands-400.ttf

fa-brands-400.ttf

686 ms

fa-brands-400.ttf

fa-brands-400.ttf

668 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

611 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

608 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

606 ms

fa-regular-400.ttf

fa-regular-400.ttf

746 ms

fa-solid-900.ttf

fa-solid-900.ttf

645 ms

js

js

41 ms

search.js

search.js

4 ms

geometry.js

geometry.js

7 ms

main.js

main.js

12 ms

twincitiespawn.com

twincitiespawn.com

405 ms

TC.png

TC.png

67 ms

TC-Pawn-Slider-2021la.jpg

TC-Pawn-Slider-2021la.jpg

358 ms

Games-2.jpg

Games-2.jpg

354 ms

Jewlery.jpg

Jewlery.jpg

299 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

65 ms

core-laptop.css

core-laptop.css

64 ms

core-tablet.css

core-tablet.css

64 ms

core-mobile.css

core-mobile.css

66 ms

codevzplus-tablet.css

codevzplus-tablet.css

64 ms

codevzplus-mobile.css

codevzplus-mobile.css

65 ms

Accessibility Review

twincitiespawn.com accessibility score

93

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

twincitiespawn.com best practices score

83

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

SEO Factors

twincitiespawn.com SEO score

86

Search Engine Optimization Advices

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

twincitiespawn.com

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