PCBenchmark/Results/Intel Core i5-7200U + Intel Iris Pro Graphics 6200 browser benchmark
PC SCORE4OUT OF 100
SYSTEM GRADEE
Fair quality run 16 September 2026 · 12:50 EEST

Intel Core i5-7200U+Intel Iris Pro Graphics 6200

A completed baseline run. Review quality and raw metrics before comparing it.

SUITEFULL SYSTEM MODEQUICK GPU APIWebGPU ENGINE1.2.1 SCORE SCALEPROVISIONAL R4 DURATION00:31
Run same suite
01 / WORKLOAD BREAKDOWN

Performance by workload.

CPU and GPU use the current adaptive scale for the same workload, mode and graphics backend. When a faster validated device becomes the reference, older comparable scores are projected onto the new scale without changing their raw measurements. VRAM remains a pass/fail diagnostic.

CPU5

Processor throughput

Single thread
150.78 Mops/s
Multi thread
184.12 Mops/s
Compression proxy
52.7 MB/s
GPU0

Graphics throughput

Estimated shader work
20.2 G shader ops/s
Render throughput
0.0 FPS
Frame time p95
0.00 ms
MEMORY12

System memory

Effective bandwidth
4.18 GB/s
Latency proxy
152.7 ns
Browser RAM class
8 GB class
VRAMPASS

GPU-memory diagnostic

Transfer bandwidth
0.07 GB/s
Tested allocation
128 MB
Validation errors
0 errors
02 / RELATIVE PERFORMANCE

What sits above and below this hardware.

Each ladder uses one consistent source. Validated PCBenchmark medians take priority when the matching workload cohort has enough approved runs; until then, the report shows a clearly marked catalog estimate.

CPU POSITION

Intel Core i5-7200U comparison ladder

ESTIMATE

Specification-based estimateApproximate browser CPU capacity derived from official core, thread and clock specifications for Kaby Lake desktop processors. It is not a measured benchmark.

  1. Intel Xeon E3-1505M v6Kaby Lake · 4 cores / 8 threads · 2017
    +65.4%higher estimate
  2. Intel Core i7-7500UKaby Lake · 2 cores / 4 threads · 2016
    +10.9%higher estimate
  3. Intel Core i5-7200UKaby Lake · 2 cores / 4 threads · 2016
    BASECATALOG REFERENCE
  4. Intel Core i7-7Y75Kaby Lake · 2 cores / 4 threads · 2016
    −15.8%lower estimate
  5. Intel Core m3-7Y32Kaby Lake · 2 cores / 4 threads · 2017
    −29.4%lower estimate
GPU POSITION

Intel Iris Pro Graphics 6200 comparison ladder

ESTIMATE

Theoretical FP32 estimatePercentages compare theoretical FP32 compute within the desktop GPU catalog; they are not measured PCBenchmark or gaming performance.

  1. Intel Arc A310Alchemist(Arc 3) · 4 GB VRAM · 2022
    +220.2%higher estimate
  2. Intel Xe DG1Xe Graphics · 4 GB VRAM · 2020
    +135.7%higher estimate
  3. Intel H3C XG310H3C Graphics · 8 GB VRAM · 2020
    +101.2%higher estimate
  4. Intel Iris Pro Graphics 6200HD Graphics(Broadwell) · 2014
    BASECATALOG REFERENCE

No slower peer is available in this comparison set.

03 / STABILITY100.0%

Sustained-load signal

This signal summarizes frame delivery during the timed graphics phase. It can reveal an inconsistent run, but it is not a temperature sensor.

COMPLETEDNO SAMPLE WINDOW31 SEC DROPPED FRAMES0.00%
04 / ENVIRONMENTRUN CONTEXT

What the browser disclosed

Selected suite
Full system
Platform family
Windows
Logical processors
4
Browser RAM class
8 GB · rounded/capped
Graphics API
WebGPU
Run quality
Fair · 57/100
Score fingerprint
adaptive-v2.0 / 1.2.1
Current adaptive scale
Provisional revision 4 / 28 August 2026
i
BROWSER BENCHMARK, NOT HARDWARE ATTESTATION

Read this result in its proper context.

It measures this browser’s execution path under the conditions of this run. Cooling, power mode, drivers, background processes and browser updates can change the outcome. CPU/GPU names may be supplied manually or matched to the catalog from a browser hint. Compare only matching suite, mode, engine version and graphics backend. NOT RUN categories were not measured and are not zero-performance results.

Read methodology & limitations
05 / RAW RESULT DATAInspect JSON +
{
    "test_suite": "all",
    "test_mode": "quick",
    "duration_ms": 31405,
    "system": {
        "cpu_name": "Intel Core i5-7200U",
        "gpu_name": "Intel Iris Pro Graphics 6200",
        "logical_cores": 4,
        "memory_gb": 8,
        "platform": "windows",
        "gpu_api": "webgpu",
        "processor_id": 1604,
        "graphics_card_id": 1938
    },
    "metrics": {
        "stability": {
            "duration_seconds": 31,
            "completed": false,
            "dropped_frames_percent": 0
        },
        "cpu": {
            "single_core_ops_per_second": 150784629.495,
            "multi_core_ops_per_second": 184118682.783,
            "compression_mb_per_second": 52.658
        },
        "memory": {
            "bandwidth_gbps": 4.179,
            "latency_ns": 152.702
        },
        "gpu": {
            "frames_per_second": 0,
            "compute_gflops": 20.197,
            "frame_time_p95_ms": 0
        },
        "vram": {
            "tested_mb": 128,
            "bandwidth_gbps": 0.074,
            "errors": 0
        }
    },
    "raw_points": {
        "cpu": 2.42296751,
        "gpu": 0.01683083
    },
    "original_scores": {
        "cpu": 5,
        "gpu": 0,
        "memory": 12,
        "vram": 0,
        "overall": 4,
        "grade": "E"
    },
    "current_scores": {
        "cpu": 5,
        "gpu": 0,
        "memory": 12,
        "vram": 0,
        "overall": 4,
        "grade": "E",
        "snapshot_revision": 4
    },
    "runner_version": "1.2.1",
    "workload_signature": "browser-1.2",
    "scoring_version": "adaptive-v2.0"
}
SAME SUITE, FRESH CONDITIONS

Think this system can do better?

Close heavy apps, connect power, keep the tab visible and run the same Full system suite and Quick mode again.

Run it again