Tools & Wizards About Us
srp.tw screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

srp.tw

Plate Heat Exchanger Manufacturer and Supplier for Industries - Taiwan SRP

Page Load Speed

5.3 sec in total

First Response

596 ms

Resources Loaded

4.4 sec

Page Rendered

305 ms

srp.tw screenshot

About Website

Visit srp.tw now to see the best up-to-date SRP content and also check out these interesting facts you probably never knew about srp.tw

Taiwan SRP is the heat exchanger manufacturing company in Taiwan. We offer gasket, shell and plate heat exchangers, with compact heat exchanger solutions and services worldwide.

Visit srp.tw

Key Findings

We analyzed Srp.tw page load time and found that the first response time was 596 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

srp.tw performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

43/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value1,970 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.169

70/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

srp.tw

596 ms

www.srp.tw

1272 ms

general.css

982 ms

md.css

413 ms

owl.css

611 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 59% of them (37 requests) were addressed to the original Srp.tw, 10% (6 requests) were made to Youtube.com and 6% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Srp.tw.

Page Optimization Overview & Recommendations

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

Content Size

1.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Srp.tw main page is 1.9 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 25.3 kB

  • Original 36.3 kB
  • After minification 34.3 kB
  • After compression 11.1 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 25.3 kB or 70% of the original size.

Image Optimization

-10%

Potential reduce by 140.4 kB

  • Original 1.4 MB
  • After minification 1.3 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. SRP images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 47.5 kB

  • Original 367.9 kB
  • After minification 366.7 kB
  • After compression 320.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 47.5 kB or 13% of the original size.

CSS Optimization

-27%

Potential reduce by 24.1 kB

  • Original 89.4 kB
  • After minification 82.3 kB
  • After compression 65.4 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. Srp.tw needs all CSS files to be minified and compressed as it can save up to 24.1 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (40%)

Requests Now

57

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

srp.tw

srp.tw

596 ms

www.srp.tw

www.srp.tw

1272 ms

general.css

general.css

982 ms

md.css

md.css

413 ms

owl.css

owl.css

611 ms

owl.theme.css

owl.theme.css

418 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

812 ms

yui-min.js

yui-min.js

157 ms

jquery.min.js

jquery.min.js

30 ms

owl.2.0.0.min.js

owl.2.0.0.min.js

518 ms

img.min.js

img.min.js

398 ms

fitvids.js

fitvids.js

194 ms

classie.js

classie.js

211 ms

plugins.js

plugins.js

397 ms

main.js

main.js

518 ms

css

css

22 ms

analytics.js

analytics.js

95 ms

embed

embed

269 ms

xXzSkowecZM

xXzSkowecZM

184 ms

E2kr7V9neGI

E2kr7V9neGI

484 ms

logo-xl.png

logo-xl.png

210 ms

logo-xs.png

logo-xs.png

208 ms

logo-second.png

logo-second.png

208 ms

logo-third.png

logo-third.png

207 ms

menu.svg

menu.svg

207 ms

navbg.png

navbg.png

209 ms

about_title.jpg

about_title.jpg

685 ms

news_title.png

news_title.png

684 ms

Semi-Welding%20Gasket%20Plate%20Heat%20Exchanger-small.png

Semi-Welding%20Gasket%20Plate%20Heat%20Exchanger-small.png

1482 ms

Gasket%20Plate%20Heat%20Exchanger-small.jpg

Gasket%20Plate%20Heat%20Exchanger-small.jpg

1429 ms

Sub-Station%20Unit.jpg

Sub-Station%20Unit.jpg

1011 ms

1448444303.jpg

1448444303.jpg

739 ms

1448443560.png

1448443560.png

1569 ms

DSCN3393.JPG

DSCN3393.JPG

1448 ms

1459512303.png

1459512303.png

1399 ms

1468420279.jpg

1468420279.jpg

1418 ms

1483175212.jpg

1483175212.jpg

1612 ms

contact_title.png

contact_title.png

1625 ms

contact_call.png

contact_call.png

1620 ms

contact_fax.png

contact_fax.png

1649 ms

contact_mail.png

contact_mail.png

1686 ms

contact_address.png

contact_address.png

1759 ms

icon_facebook.png

icon_facebook.png

1812 ms

collect

collect

25 ms

js

js

65 ms

www-player.css

www-player.css

38 ms

www-embed-player.js

www-embed-player.js

59 ms

base.js

base.js

86 ms

js

js

449 ms

ad_status.js

ad_status.js

584 ms

XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js

XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js

151 ms

embed.js

embed.js

99 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

334 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

338 ms

search.js

search.js

274 ms

geometry.js

geometry.js

276 ms

main.js

main.js

402 ms

id

id

187 ms

Create

Create

201 ms

Create

Create

305 ms

GenerateIT

GenerateIT

16 ms

GenerateIT

GenerateIT

17 ms

xs.css

xs.css

217 ms

Accessibility Review

srp.tw accessibility score

74

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

srp.tw 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

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

SEO Factors

srp.tw SEO score

90

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Srp.tw can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Srp.tw 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

srp.tw

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